Re: How to prevent vacuum and reindex from deadlocking.

From: Dennis Gearon <gearond(at)cvc(dot)net>
To: Robert Creager <Robert_Creager(at)LogicalChaos(dot)org>
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 15:25:33
Message-ID: 3F3A586D.70505@cvc.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

In general, the documentation is not direct. When it is, it often is using database theory language, masters level database engineer language.

Robert Creager wrote:

> 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
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Josh Berkus 2003-08-13 15:34:58 Re: Commercial support?
Previous Message Jason Priebe 2003-08-13 15:04:14 more timeofday() and "set time zone" weirdness