Re: Hot standby and removing VACUUM FULL - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Hot standby and removing VACUUM FULL
Date
Msg-id 1259919027.13774.37808.camel@ebony
Whole thread Raw
In response to Re: Hot standby and removing VACUUM FULL  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Fri, 2009-12-04 at 11:22 +0200, Heikki Linnakangas wrote:

> Could you just mark the transaction as committed when you see the 1st
> commit record, but leave the XID in the known-assigned list and not
> release locks? That would emulate pretty closely what happens in the master.

OK, works for me. Thanks.

I thought of that before and dismissed it, clearly before my morning
coffee, but it works because we still hold the lock on the table so
nobody can actually read the now visible new rows. Cool.

-- Simon Riggs           www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Hot standby and removing VACUUM FULL
Next
From: decibel
Date:
Subject: Re: Block-level CRC checks