| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Incomplete freezing when truncating a relation during vacuum |
| Date: | 2013-11-30 16:48:09 |
| Message-ID: | 20131130164809.GF31100@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-11-30 11:18:09 -0500, Tom Lane wrote:
> Indeed. We already said that this release was being done *now* because
> of the replication bug, and I see no reason to change that.
FWIW, I think the two other data corrupting bugs, "incomplete freezing
due to truncation" (all branches) and freezing overall (in 9.3), are at
least as bad because they take effect on the primary.
Not saying that because of my involvement, but because I think they need
to be presented at least as prominent in the release notes.
They bugs themselves are all fixed in the relevant branches, but I do
think we need to talk about about how to detect and fix possible
corruption.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-11-30 16:50:57 | Re: Incomplete freezing when truncating a relation during vacuum |
| Previous Message | Kevin Grittner | 2013-11-30 16:41:32 | Re: MultiXact bugs |