| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hot standby and removing VACUUM FULL |
| Date: | 2009-12-04 09:30:27 |
| Message-ID: | 1259919027.13774.37808.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | decibel | 2009-12-04 09:32:22 | Re: Block-level CRC checks |
| Previous Message | Heikki Linnakangas | 2009-12-04 09:22:40 | Re: Hot standby and removing VACUUM FULL |