Re: Back-branch update releases coming in a couple weeks
Andres Freund <andres@2ndquadrant.com>
From: Andres Freund <andres@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Date: 2013-02-01T13:50:28Z
Lists: pgsql-hackers
On 2013-01-22 22:19:25 -0500, Tom Lane wrote: > Since we've fixed a couple of relatively nasty bugs recently, the core > committee has determined that it'd be a good idea to push out PG update > releases soon. The current plan is to wrap on Monday Feb 4 for public > announcement Thursday Feb 7. If you're aware of any bug fixes you think > ought to get included, now's the time to get them done ... I think the patch in http://www.postgresql.org/message-id/20130130145521.GB3355@awork2.anarazel.de should get applied before the release if we decide it should be backpatched. And I think backpatching makes sense, the amount of useless full-table-scans will sure hurt more than some workload thats accidentally fixed by this. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
-
Consistency check should compare last record replayed, not last record read.
- 970fb12de121 9.3.0 cited
-
Update minimum recovery point on truncation.
- 7bffc9b7bf9e 9.3.0 cited