Re: VACUUM and transactions in different databases

Bill Moran <wmoran@collaborativefusion.com> writes:
> In response to Alvaro Herrera <alvherre@commandprompt.com>:
>> Of course they are able to complete, but the point is that they would
>> not remove the tuples that would be visible to that idle open
>> transaction.

> I would expect that, but the OP claimed that vacuum full waited until
> the other transaction was finished.

No, she didn't claim that.  As far as I see she was just complaining
about the failure to remove dead tuples:

> > > > If I have a running transaction in database1 and try to vacuum
> > > > database2 but the dead tuples in database2 cannot be removed.

            regards, tom lane