From: | Robert Creager <Robert_Creager(at)LogicalChaos(dot)org> |
---|---|
To: | 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-13 13:40:07 |
Message-ID: | 20030813074007.4285a60e.Robert_Creager@LogicalChaos.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 13 Aug 2003 01:45:07 -0400
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Gamache | 2003-08-13 13:42:35 | Re: Viewing Client Connections.. |
Previous Message | Tim Edwards | 2003-08-13 13:32:10 | Re: Sorting Problem |