Skip site navigation (1) Skip section navigation (2)

Re: Prepared transactions vs novice DBAs, again

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, jd(at)commandprompt(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Prepared transactions vs novice DBAs, again
Date: 2009-04-22 21:15:11
Message-ID: 603c8f070904221415p58f01ec8t45d7d34f934941bf@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Apr 22, 2009 at 2:58 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> Tom Lane wrote:
>>
>> Does a prepared xact still block vacuum cleanup in HEAD, or has that
>> been fixed since 8.2?
>
> It still does. A prepared xact is just like a idle-in-transaction backend as
> far as vacuum is concerned.

Is that really necessary? It's true that you can't vacuum away any
rows whose xmin is that of the prepared xact, but it seems like you
wouldn't need to keep rows just because they were *visible* to the
prepared xact.  Once prepared, it's no longer capable of reading them.

...Robert

In response to

Responses

pgsql-hackers by date

Next:From: Hiroshi InoueDate: 2009-04-22 21:35:28
Subject: Re: trouble with to_char('L')
Previous:From: Tom LaneDate: 2009-04-22 20:26:49
Subject: Re: Prepared transactions vs novice DBAs, again

Privacy Policy | About PostgreSQL
Copyright © 1996-2013 The PostgreSQL Global Development Group