Re: How to prevent vacuum and reindex from deadlocking.

From: Robert Creager <Robert_Creager(at)LogicalChaos(dot)org>
To: gearond(at)cvc(dot)net
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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 04:06:04
Message-ID: 20030812220604.1eecae67.Robert_Creager@LogicalChaos.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 12 Aug 2003 08:13:59 -0700
Dennis Gearon <gearond(at)cvc(dot)net> said something like:

> Postgres itself doesn't support nested transactions.
>

Yea, I just convinced myself of that. The first time I read the docs, that's
what I thought. Then I convinced myself when I re-read them that it was just a
warning, and a new transaction was started. But I just tried it, and they're
not...

Thanks for point that out to me. I dare say that the BEGIN documentation is
unclear to me, even knowing what I know now. Why not just explictly say "Nested
transactions are not supported", rather than "... The current transaction is
not affected". Alright, maybe I still read at Junior High level.

Cheers,
Rob

--
21:59:11 up 11 days, 14:43, 4 users, load average: 2.17, 2.10, 2.02

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jerome Macaranas 2003-08-13 05:03:55 Viewing Client Connections..
Previous Message Envex Developments 2003-08-13 03:51:09 Installing DBD::Pg Perl module locally