On July 16, 2016 8:49:06 AM PDT, Tom Lane <t...@sss.pgh.pa.us> wrote: >Amit Kapila <amit.kapil...@gmail.com> writes: >> On Sat, Jul 16, 2016 at 7:02 AM, Andres Freund <and...@anarazel.de> >wrote: >>> I think we have two choices how to deal with that: First, we can add >a >>> new flags variable to xl_heap_lock similar to >>> xl_heap_insert/update/... and bump page magic, > >> +1 for going in this way. This will keep us consistent with how >clear >> the visibility info in other places like heap_xlog_update(). > >Yeah. We've already forced a catversion bump for beta3, and I'm about >to go fix PG_CONTROL_VERSION as well, so there's basically no downside >to doing an xlog version bump as well. At least, not if you can get it >in before Monday.
OK, Cool. Will do it later today. Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
