Re: How to prevent vacuum and reindex from deadlocking. - Mailing list pgsql-general

From Robert Creager
Subject Re: How to prevent vacuum and reindex from deadlocking.
Date
Msg-id 20030813074007.4285a60e.Robert_Creager@LogicalChaos.org
Whole thread Raw
In response to Re: How to prevent vacuum and reindex from deadlocking.  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
List pgsql-general
On Wed, 13 Aug 2003 01:45:07 -0400
Alvaro Herrera <alvherre@dcc.uchile.cl> said something like:

>
> You have to keep in mind that inside PL/pgSQL, the "BEGIN" keyword has a
> different meaning, unrelated to the BEGIN keyword in SQL.  In PL/pgSQL,
> BEGIN starts a code block, and has nothing to do at all with
> transactions.
>
> (I _think_ the original question had something to do with a PL/pgSQL
> function -- if this is not the case, please ignore.)
>

Na, it was Tom's suggestion of using a begin/lock table/reindex/commit to
resolve my deadlock problem.  Unfortunately, I was already within a transaction.

Thanks,
Rob

--
 07:26:01 up 12 days, 10 min,  4 users,  load average: 5.38, 4.25, 3.74

Attachment

pgsql-general by date:

Previous
From: "Tim Edwards"
Date:
Subject: Re: Sorting Problem
Next
From: Chris Gamache
Date:
Subject: Re: Viewing Client Connections..