| From: | Andrew Borodin <borodin(at)octonica(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| 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 10:18:20 |
| Message-ID: | CAJEAwVGdQXjYhdX=Q4r=jx6KGbRKBC-hCF_gO5nmaxdYPHekQQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>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.
Here is a patch with updated GiST README.
I haven't found apropriate place to describe PageIndexTupleOverwrite
function in docs, since all it's siblings are described only in the
code.
Code comments describing this function are coherent with others
(PageAddItem, PageIndexTupleDelete).
Best regards, Andrey Borodin, Octonica & Ural Federal University.
| Attachment | Content-Type | Size |
|---|---|---|
| XLog-magic-bump.patch | application/octet-stream | 765 bytes |
| PageIndexTupleOverwrite v5.patch | application/octet-stream | 8.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-07-24 12:18:45 | Re: Re: GiST optimizing memmoves in gistplacetopage for fixed-size updates [PoC] |
| Previous Message | Amit Kapila | 2016-07-24 07:10:34 | Re: Curing plpgsql's memory leaks for statement-lifespan values |