How to prevent vacuum and reindex from deadlocking.

From: Robert Creager <Robert_Creager(at)LogicalChaos(dot)org>
To: pgsql-general(at)postgresql(dot)org <pgsql-general(at)postgresql(dot)org>
Subject: How to prevent vacuum and reindex from deadlocking.
Date: 2003-08-10 20:50:10
Message-ID: 20030810145010.23e10340.Robert_Creager@LogicalChaos.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


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 loosing the deadlock.

Is there a way I can prevent this from happening? I can obviously
acquire a LOCK before doing the REINDEX (which one?), but it looks like
this should be happening anyway by both the VACUUM and REINDEX
statements.

Help?
Rob

--
14:38:15 up 9 days, 7:23, 4 users, load average: 1.09, 1.10, 0.86

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Robert Creager 2003-08-10 20:54:49 7.4Beta1 "failed to create socket: Address family not supported by protocol"
Previous Message Chris Travers 2003-08-10 20:20:27 Re: Moving from MySQL