| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Freezing without write I/O |
| Date: | 2013-08-30 18:34:37 |
| Message-ID: | 20130830183437.GB6794@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Heikki,
On 2013-08-27 18:56:15 +0300, Heikki Linnakangas wrote:
> Here's an updated patch. The race conditions I mentioned above have been
> fixed.
Thanks for posting the new version!
I have a quick question: The reason I'd asked about the status of the
patch was that I was thinking about the state of the "forensic freezing"
patch. After a quick look at your proposal, we still need to freeze in
some situations (old & new data on the same page basically), so I'd say
it still makes sense to apply the forensic freezing patch, right?
Differing Opinions?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2013-08-30 18:57:45 | Re: ENABLE/DISABLE CONSTRAINT NAME |
| Previous Message | Andres Freund | 2013-08-30 18:29:16 | Re: Add database to PGXACT / per database vacuuming |