Re: Prepared Xacts and Vacuum question - Mailing list pgsql-hackers

From Satoshi Nagayasu
Subject Re: Prepared Xacts and Vacuum question
Date
Msg-id fa3bffeb0602191549w49f69dfgbf3c9b5be4122a8a@mail.gmail.com
Whole thread Raw
In response to Re: Prepared Xacts and Vacuum question  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2/20/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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 completely understand that, however it can be occured...
Prepared xacts never die...

> > I think the prepared xacts on any database mustn't affect to another database.
>
> Wrong, consider updates to shared catalogs.

But my prepared xact did not affect to the system catalogs....

I think some messages should be shown to the DBA by the backend,
because DBA will get in trouble without any information about it.

And also it should be noted on the manual.

Thanks.
--
NAGAYASU Satoshi <snaga@snaga.org>


pgsql-hackers by date:

Previous
From: Albert Chin
Date:
Subject: AC_REPLACE_FUNCS([getaddrinfo]) in 8.1.3
Next
From: elein
Date:
Subject: Re: Domains and supporting functions