| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | KÖPFERL Robert <robert(dot)koepferl(at)sonorys(dot)at> |
| Cc: | "'dpandey(at)secf(dot)com'" <dpandey(at)secf(dot)com>, 'Richard Huxton' <dev(at)archonet(dot)com>, pgsql-general(at)postgresql(dot)org, 'PostgreSQL' <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: index row size 2728 exceeds btree maximum, 27 |
| Date: | 2005-06-02 12:31:50 |
| Message-ID: | 20050602123150.GB6785@wolff.to |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
On Thu, Jun 02, 2005 at 14:08:54 +0200,
KÖPFERL Robert <robert(dot)koepferl(at)sonorys(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tony Caduto | 2005-06-02 12:34:34 | Re: writting a large store procedure |
| Previous Message | Bruno Wolff III | 2005-06-02 12:26:32 | Re: interval integer comparison |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2005-06-02 12:35:20 | Re: index row size 2728 exceeds btree maximum, 2713 |
| Previous Message | Dinesh Pandey | 2005-06-02 12:18:47 | Re: [SQL] index row size 2728 exceeds btree maximum, 2713 |