Search Postgresql Archives

Re: VACUUM and transactions in different databases

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bill Moran <wmoran@xxxxxxxxxxxxxxxxxxxxxxx> writes:
> In response to Alvaro Herrera <alvherre@xxxxxxxxxxxxxxxxx>:
>> 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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux