Search Postgresql Archives

Re: [SQL] index row size 2728 exceeds btree maximum, 27

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jun 02, 2005 at 13:40:53 +0100,
  Richard Huxton <dev@xxxxxxxxxxxx> wrote:
> 
> Actually, Dinesh didn't mention he was using this for the speed of 
> lookup. He'd defined the columns as being the PRIMARY KEY, presumably 
> because he feels they are/should be unique. Given that they are rows 
> from a logfile, I'm not convinced this is the case.

Even for case you could still use hashes. The odds of a false collision
using SHA-1 are so small that some sort of disaster is more likely.
Another possibility is if there are a fixed number of possible messages,
is that they could be entered in their own table with a serail PK and
the other table could reference the PK.

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux