pg.ddx.io pgsql-sql@postgresql.org mailing list archivehelp / color / mirror / Atom feed
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: Thu, 02 Jun 2005 18:00:17 +0100
Message-ID: <429F3B21.9020209@archonet.com> (raw)
In-Reply-To: <20050602163542.GA23150@wolff.to>
References: <ED4E30DD9C43D5118DFB00508BBBA76EB16736@neptun.sonorys.at>
<429EFE55.3050601@archonet.com>
<20050602163542.GA23150@wolff.to>
Bruno Wolff III wrote:
> 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.
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.
--
Richard Huxton
Archonet Ltd
view thread (18+ messages) latest in thread
Message-ID: <429F3B21.9020209@archonet.com> Permalink: ../429F3B21.9020209@archonet.com/ Also on: postgresql.org/message-id/429F3B21.9020209@archonet.com ·
reply
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: <429F3B21.9020209@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