| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Changing WAL Header to reduce contention during ReserveXLogInsertLocation() |
| Date: | 2018-01-13 01:49:01 |
| Message-ID: | 623.1515808141@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Claudio Freire <klaussfreire(at)gmail(dot)com> writes:
> On Sat, Dec 30, 2017 at 7:32 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> So we can't completely remove xl_prev field, without giving up some
>> functionality.
> Or, you can use the lower 16-bits of the previous record's CRC
Hmm ... that is an interesting idea, but I'm not sure it helps much
towards Simon's actual objective. AIUI the core problem here is the
contention involved in retrieving the previous WAL record's address.
Changing things so that we need the previous record's CRC isn't really
gonna improve that --- if anything, it'll be worse, because the
record's address can (in principle) be known sooner than its CRC.
Still, if we were just looking to shave some bits off of WAL record
headers, it might be possible to do something with this idea.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2018-01-13 02:06:27 | Re: Changing WAL Header to reduce contention during ReserveXLogInsertLocation() |
| Previous Message | Tom Lane | 2018-01-13 01:16:25 | Re: [HACKERS] Planning counters in pg_stat_statements |