Re: Reviewing freeze map code
От | Tom Lane |
---|---|
Тема | Re: Reviewing freeze map code |
Дата | |
Msg-id | 25549.1468684146@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Reviewing freeze map code (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: Reviewing freeze map code
|
Список | pgsql-hackers |
Amit Kapila <amit.kapila16@gmail.com> writes: > On Sat, Jul 16, 2016 at 7:02 AM, Andres Freund <andres@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. regards, tom lane
В списке pgsql-hackers по дате отправления: