Re: Prepared Xacts and Vacuum question

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Satoshi Nagayasu" <snaga(at)snaga(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Prepared Xacts and Vacuum question
Date: 2006-02-19 17:10:16
Message-ID: 11536.1140369016@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Satoshi Nagayasu" <snaga(at)snaga(dot)org> writes:
> When I was playing with VACUUM, I found that if I have prepared xacts
> on the database A, I can't vacuum full on the database B.

A prepared xact is the same as an open xact as far as vacuum is
concerned. It's a bad idea to sit on either open or prepared xacts
for long periods ...

> I think the prepared xacts on any database mustn't affect to another database.

Wrong, consider updates to shared catalogs.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-02-19 17:13:48 Re: possible design bug with PQescapeString()
Previous Message Andrew Dunstan 2006-02-19 16:38:12 Re: implement prepared queries in plperl