From: | Robert Creager <Robert_Creager(at)LogicalChaos(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How to prevent vacuum and reindex from deadlocking. |
Date: | 2003-08-12 03:58:32 |
Message-ID: | 20030811215832.7458618c.Robert_Creager@LogicalChaos.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 11 Aug 2003 11:05:57 -0400
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> said something like:
>
> If you really want to rebuild only the one index, I think this will work:
>
> begin;
> lock table tab;
> reindex index ndx;
> commit;
Figures. It appears that DBD::Pg doesn't supported nested transactions (I was
already in a transaction).
DBD::Pg::db begin_work failed: Already in a transaction at
/tass/bin/importSList.pl line 445.
Unfortunatly, it does take longer overall because of the second index on the
table, but it always works ;-) 'Nother duh moment, delete the second index,
and then it works just fine speed wise. Guess I need to re-examine my index
usage...
Thanks,
Rob
--
21:16:30 up 10 days, 14:01, 4 users, load average: 3.37, 3.34, 3.19
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2003-08-12 04:28:49 | Re: Update of foreign key values |
Previous Message | Bruce Momjian | 2003-08-12 02:50:36 | Re: 7.4Beta1 "failed to create socket: Address family not |