Re: Release schedule for 9.3.3?
Andres Freund <andres@2ndquadrant.com>
From: Andres Freund <andres@2ndquadrant.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2014-02-14T18:51:24Z
Lists: pgsql-hackers
On 2014-02-14 13:33:46 -0500, Josh Berkus wrote: > On 02/14/2014 01:11 PM, Andres Freund wrote: > > Hi, > > > > On 2014-02-14 13:08:34 -0500, Josh Berkus wrote: > >> Do the 9.3.3 replication fixes mean that users should reclone their > >> replicas, like 9.3.2 did? Or not? > > > > Which replication replication fixes are you referring to? > > http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=ebde6c40148c9f811f7c6d35f67e7ea3ce2d9b34 > > ? > > If so, no, that doesn't require a reclone. > > Hmmm. I thought there were also 9.3-only replication fixes in this > release? No? I don't know any. There's further multixact fixes but AFAIK there's nothing replication specific, and they shouldn't cause problems but lost row locks in some edge cases. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
-
Fix multiple bugs in index page locking during hot-standby WAL replay.
- ebde6c40148c 9.3.3 cited
-
Don't ignore tuple locks propagated by our updates
- db1014bc46de 9.3.3 cited
-
Improve concurrency of foreign key locking
- 0ac5ad5134f2 9.3.0 cited