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 20030812220604.1eecae67.Robert_Creager@LogicalChaos.org
Whole thread Raw
In response to Re: How to prevent vacuum and reindex from deadlocking.  (Dennis Gearon <gearond@cvc.net>)
Responses Re: How to prevent vacuum and reindex from deadlocking.  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
Re: How to prevent vacuum and reindex from deadlocking.  (Dennis Gearon <gearond@cvc.net>)
List pgsql-general
On Tue, 12 Aug 2003 08:13:59 -0700
Dennis Gearon <gearond@cvc.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

Attachment

pgsql-general by date:

Previous
From: "Envex Developments"
Date:
Subject: Installing DBD::Pg Perl module locally
Next
From: Jerome Macaranas
Date:
Subject: Viewing Client Connections..