|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Chapman Flack <chap(at)anastigmatix(dot)net>|
|Subject:||Re: [HACKERS] AdvanceXLInsertBuffer vs. WAL segment compressibility|
|Views:||Raw Message | Whole Thread | Download mbox|
Chapman Flack <chap(at)anastigmatix(dot)net> writes:
> On 03/25/18 23:27, Stephen Frost wrote:
>> AdvanceXLInsertBuffer() does quite a bit, so I'm a bit surprised to see
>> this simply removing that call, you're confident there's nothing done
>> which still needs doing..?
> My belief from looking at the code was that AdvanceXLInsertBuffer() is among
> the things GetXLogBuffer() does, so calling both would result in two calls
> to the former (which I don't believe would hurt, it would only
> do enough work the second time to determine it had already been done).
If that's the argument, why is the WALInsertLockUpdateInsertingAt(CurrPos)
call still there? GetXLogBuffer() would do that too.
In any case, the new comment seems very poorly written, as it fails to
explain what's going on, and the reference to a function that is not
actually called from the vicinity of the comment doesn't help. I'd
suggest something like "GetXLogBuffer() will fetch and initialize the
next WAL page for us. But it initializes the page header to nonzero,
which is undesirable because X, so we then reset the header to zero".
It might also be worth explaining how you know that the new page's
header is short not long.
regards, tom lane
|Next Message||Dmitry Ivanov||2018-03-26 16:48:19||Re: new function for tsquery creartion|
|Previous Message||Fujii Masao||2018-03-26 16:32:41||Re: Using base backup exclusion filters to reduce data transferred with pg_rewind|