From: Richard Huxton <dev@archonet.com>
To: Bruno Wolff III <bruno@wolff.to>
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: Fri, 03 Jun 2005 08:22:20 +0100
Message-ID: <42A0052C.6040505@archonet.com> (raw)
In-Reply-To: <20050602193324.GA2861@wolff.to>
References: <ED4E30DD9C43D5118DFB00508BBBA76EB16736@neptun.sonorys.at>
<429EFE55.3050601@archonet.com>
<20050602163542.GA23150@wolff.to>
<429F3B21.9020209@archonet.com>
<20050602193324.GA2861@wolff.to>
Bruno Wolff III wrote:
> On Thu, Jun 02, 2005 at 18:00:17 +0100,
> Richard Huxton <dev@archonet.com> wrote:
>
>>Certainly, but if the text in the logfile row is the same, then hashing
>>isn't going to make a blind bit of difference. That's the root of my
>>concern, and something only Dinesh knows.
>
>
> Sure it is. Because the hash can be used in the primary key instead of
> of the error message which should reduce the size of the key enough
> that he can use a btree index.
Sorry - obviously not being clear. Since he's using the index via a
primary key he'll need the columns that key is over to be unique. If the
columns fail that test in the real world, hashing will replace the
index-size error with an "unable to insert duplicates" error.
--
Richard Huxton
Archonet Ltd
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: dev@archonet.com, bruno@wolff.to, robert.koepferl@sonorys.at, dpandey@secf.com
Subject: Re: [SQL] index row size 2728 exceeds btree maximum, 27
In-Reply-To: <42A0052C.6040505@archonet.com>
* 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