From: Bruno Wolff III <bruno@wolff.to>
To: KÖPFERL Robert <robert.koepferl@sonorys.at>
Cc: 'dpandey@secf.com' <dpandey@secf.com>
Cc: Richard Huxton <dev@archonet.com>
Cc: pgsql-general@postgresql.org, 'PostgreSQL' <pgsql-sql@postgresql.org>
Subject: Re: index row size 2728 exceeds btree maximum, 27
Date: Thu, 2 Jun 2005 07:31:50 -0500
Message-ID: <20050602123150.GB6785@wolff.to> (raw)
In-Reply-To: <ED4E30DD9C43D5118DFB00508BBBA76EB16736@neptun.sonorys.at>
References: <ED4E30DD9C43D5118DFB00508BBBA76EB16736@neptun.sonorys.at>
On Thu, Jun 02, 2005 at 14:08:54 +0200,
KÖPFERL Robert <robert.koepferl@sonorys.at> wrote:
> To me it seems that the definer of this table missed the concept index ...
> or the concept database
> One usually looks up data using a key, but if the whole row is the key, what
> data shall be looked up.
You sometimes do want to make a whole role a key to avoid duplicate keys.
A common case is when you use a table to connect two other tables with
a many to many relation.
It would be rare to want to do that with large text values though.
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, robert.koepferl@sonorys.at, dpandey@secf.com, dev@archonet.com
Subject: Re: index row size 2728 exceeds btree maximum, 27
In-Reply-To: <20050602123150.GB6785@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