Because of global tables, I don't think we make any distinction between
xids of the same database and those of a different database, so the
current behavior seems correct.
---
Satoshi Nagayasu wrote:
> Hi all,
>
> When I wa
On 2/20/06, Tom Lane <[EMAIL PROTECTED]> 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...
> >
"Satoshi Nagayasu" <[EMAIL PROTECTED]> 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 pr
Hi all,
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.
Scenario:
1.) Prepare some transaction on "testdb" database.
2.) Create database "pgbench".
3.) Run "pgbench -i" to load pgbench data on "pgbench" database
4.) D
