| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Dinesh Pandey <dpandey(at)secf(dot)com> |
| Cc: | 'Ramakrishnan Muralidharan' <ramakrishnanm(at)pervasive-postgres(dot)com>, pgsql-general(at)postgresql(dot)org, 'PostgreSQL' <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: index row size 2728 exceeds btree maximum, 2713 |
| Date: | 2005-06-02 12:35:20 |
| Message-ID: | 20050602123520.GC6785@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
On Thu, Jun 02, 2005 at 17:48:47 +0530,
Dinesh Pandey <dpandey(at)secf(dot)com> wrote:
> Yes I am storing some "error messages" in data column, and the PK columns
> are party of search criteria.
If you need to be able to search based on the entire stored error message,
than you might try adding an indexed hash column to the table and using that
to speed up searches. You can still compare the full string in case you
have a hash collision, but those should be very rare.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2005-06-02 12:40:53 | Re: [SQL] index row size 2728 exceeds btree maximum, 27 |
| Previous Message | Tony Caduto | 2005-06-02 12:34:34 | Re: writting a large store procedure |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2005-06-02 12:40:53 | Re: [SQL] index row size 2728 exceeds btree maximum, 27 |
| Previous Message | Bruno Wolff III | 2005-06-02 12:31:50 | Re: index row size 2728 exceeds btree maximum, 27 |