Re: [GENERAL] How to prevent vacuum and reindex from deadlocking.

2003-08-14 Thread Robert Creager
On Mon, 11 Aug 2003 10:11:37 -0400 Tom Lane <[EMAIL PROTECTED]> said something like: > Robert Creager <[EMAIL PROTECTED]> writes: > > Opps, if it helps, the log of the deadlock: > > > Aug 10 14:19:36 thunder postgres[18735]: [2-1] ERROR: deadlock detected > > > Aug 10 14:19:36 thunder postgres[

Re: [GENERAL] How to prevent vacuum and reindex from deadlocking.

2003-08-14 Thread Tom Lane
Robert Creager <[EMAIL PROTECTED]> writes: > Opps, if it helps, the log of the deadlock: > Aug 10 14:19:36 thunder postgres[18735]: [2-1] ERROR: deadlock detected > Aug 10 14:19:36 thunder postgres[18735]: [2-2] DETAIL: Proc 18735 waits > for AccessExclusiveLock on relation 18028 of database 17

Re: [GENERAL] How to prevent vacuum and reindex from deadlocking.

2003-08-14 Thread Dennis Gearon
Postgres itself doesn't support nested transactions. Robert Creager wrote: On Mon, 11 Aug 2003 11:05:57 -0400 Tom Lane <[EMAIL PROTECTED]> 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.

Re: [GENERAL] How to prevent vacuum and reindex from deadlocking.

2003-08-14 Thread Robert Creager
On Sun, 10 Aug 2003 14:50:10 -0600 Robert Creager <[EMAIL PROTECTED]> said something like: > > I'm running 7.4Beta1 with pg_autovacuum. In one of my operations > which is executed frequently, a REINDEX is done after a COPY. Well, > VACUUM's are being executed by pg_autovacuum, and my app is loo