On Sun, Feb 14, 2016 at 9:03 AM, Jeff Janes <[email protected]> wrote: > I've repeated the crash/recovery/wrap-around testing with the proposed > fix in place, and this pre-existing problem seems to be fixed now, and > I have found no other problems. > > I've attached a new version, incorporating comments from Tom and Michael.
Thanks, this patch looks good to me this way. I have added an entry in the CF app to not lose track of this bug: https://commitfest.postgresql.org/9/526/ That's the most I can do. -- Michael -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
