On Tue, 2011-02-01 at 11:43 -0500, Tom Lane wrote: > Simon Riggs <si...@2ndquadrant.com> writes: > > Here's the basic patch, will work on the refactoring if no objections. > > ResolveRecoveryConflictWithDatabase works when you're not in recovery? > That seems pretty fragile at best. In any case, this is a 9.2 feature > at the earliest, please do not expect people to spend time on it now.
Err, no. Sorry if that wasn't clear. The patch works but requires refactoring, which I referred to above. What is now called ResolveRecoveryConflictWithDatabase() would be changed to a name that makes sense in both normal running and recovery. That seemed so obvious that I wouldn't be leaving it like that, so I just referred to that indirectly, which was confusing. That allows me to refactor out the code that we just spent too long discussing, so I was hoping to do that in this release. I wasn't expecting anybody else to spend time on it since it is simple and clear. I'll add it to 9.2. -- Simon Riggs http://www.2ndQuadrant.com/books/ PostgreSQL Development, 24x7 Support, Training and Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
