| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | KÖPFERL Robert <robert(dot)koepferl(at)sonorys(dot)at>, "'dpandey(at)secf(dot)com'" <dpandey(at)secf(dot)com>, pgsql-general(at)postgresql(dot)org, 'PostgreSQL' <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: [SQL] index row size 2728 exceeds btree maximum, 27 |
| Date: | 2005-06-02 19:33:24 |
| Message-ID: | 20050602193324.GA2861@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
On Thu, Jun 02, 2005 at 18:00:17 +0100,
Richard Huxton <dev(at)archonet(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ben | 2005-06-02 19:46:21 | Re: Limits of SQL |
| Previous Message | Greg Stark | 2005-06-02 18:02:10 | Re: Deleting orphaned records to establish Ref Integrity |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2005-06-03 07:22:20 | Re: [SQL] index row size 2728 exceeds btree maximum, 27 |
| Previous Message | Richard Huxton | 2005-06-02 17:00:17 | Re: [SQL] index row size 2728 exceeds btree maximum, 27 |