Re: Back-branch update releases coming in a couple weeks
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-hackers@postgresql.org
Date: 2013-01-23T03:52:03Z
Lists: pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes: > * Tom Lane (tgl@sss.pgh.pa.us) 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 ... > Should we consider including Simon's fix for an issue which Noah noted > in this thread?: > http://www.postgresql.org/message-id/CA+U5nMKBrqFxyohr=JSDpgxZ6y0nfAdmt=K3hK4Zzfqo1MHSJg@mail.gmail.com It sounds like there's something to fix there, but AFAICS the thread is still arguing about the best fix. There's time to do it non-hastily. regards, tom lane
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