| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | amborodin(at)acm(dot)org |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Sergey Mirvoda <sergey(at)mirvoda(dot)com> |
| Subject: | Re: Re: GiST optimizing memmoves in gistplacetopage for fixed-size updates [PoC] |
| Date: | 2016-07-24 12:18:45 |
| Message-ID: | CAB7nPqQ8KpphNL6jS8whjLMODgsoCa1t6CD7mCsSG43O_WrgPg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jul 24, 2016 at 7:18 PM, Andrew Borodin <borodin(at)octonica(dot)com> wrote:
>>If a feature changes the shape of WAL records, XLOG_PAGE_MAGIC is bumped to prevent any problems.
>
> I've attached patch with a bump, but, obviously, it'll be irrelevant
> after any other commit changing WAL shape.
Usually the committer in charge of reviewing such a patch would bump
it. There is no need for the patch submitter to do so. I should have
been more precise previously, sorry for my twisted words.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2016-07-24 13:12:51 | Re: Curing plpgsql's memory leaks for statement-lifespan values |
| Previous Message | Andrew Borodin | 2016-07-24 10:18:20 | Re: Re: GiST optimizing memmoves in gistplacetopage for fixed-size updates [PoC] |