Search Postgresql Archives

Re: VACUUM and transactions in different databases

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

 



On fim, 2006-12-07 at 11:28 -0500, Tom Lane wrote:
> 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.

well actually, there was also this:

On fim, 2006-12-07 at 00:57 +0100, Cornelia Boenigk wrote: 
> Hi Bill
> 
>  > Can you run a "vacuum
>  > full", and does it reclaim the space?
> 
> I tried but it hangs.

and also this:

On fim, 2006-12-07 at 01:03 +0100, Cornelia Boenigk wrote: 
>
> as soon as I committed the open transaction the hangig vacuum full 
> completed and the table was vacuumed:

gnari





[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