From: Bruno Wolff III <bruno@wolff.to>
To: Richard Huxton <dev@archonet.com>
Cc: KÖPFERL Robert <robert.koepferl@sonorys.at>
Cc: 'dpandey@secf.com' <dpandey@secf.com>
Cc: pgsql-general@postgresql.org, 'PostgreSQL' <pgsql-sql@postgresql.org>
Subject: Re: [SQL] index row size 2728 exceeds btree maximum, 27
Date: Thu, 2 Jun 2005 11:35:42 -0500
Message-ID: <20050602163542.GA23150@wolff.to> (raw)
In-Reply-To: <429EFE55.3050601@archonet.com>
References: <ED4E30DD9C43D5118DFB00508BBBA76EB16736@neptun.sonorys.at>
<429EFE55.3050601@archonet.com>
On Thu, Jun 02, 2005 at 13:40:53 +0100,
Richard Huxton <dev@archonet.com> 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: bruno@wolff.to, dev@archonet.com, robert.koepferl@sonorys.at, dpandey@secf.com
Subject: Re: [SQL] index row size 2728 exceeds btree maximum, 27
In-Reply-To: <20050602163542.GA23150@wolff.to>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox