| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Adrian Klaver <aklaver(at)comcast(dot)net> |
| Cc: | cgg007(at)yahoo(dot)com, postgresql listserv <pgsql-general(at)postgresql(dot)org>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Subject: | Re: pg_dump and ON DELETE CASCADE problem |
| Date: | 2009-12-18 17:24:31 |
| Message-ID: | 7883.1261157071@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Adrian Klaver <aklaver(at)comcast(dot)net> writes:
> On Thursday 17 December 2009 6:39:45 pm CG wrote:
>> CREATE INDEX packet_search_trigram_packet_uuid_idx
>> ON dpo.packet_search_trigram
>> USING hash
>> (packet_uuid);
> You might want to take a look at upgrading to 8.4.2 per this from the release
> notes:
Actually, what I'd recommend is dropping that hash index and replacing
it with regular btree. And the same for any other hash indexes you
have. Hash indexes simply are not production grade (yet).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Little, Douglas | 2009-12-18 17:27:26 | column level encryption & select rules |
| Previous Message | Adrian Klaver | 2009-12-18 14:41:12 | Re: pg_dump and ON DELETE CASCADE problem |