Re: log_checkpoint's "0 transaction log file(s) added" is extremely misleading - Mailing list pgsql-hackers

From Andres Freund
Subject Re: log_checkpoint's "0 transaction log file(s) added" is extremely misleading
Date
Msg-id 55E92D09-EB40-4CC0-B6BD-1A7E6B276D84@anarazel.de
Whole thread Raw
In response to Re: log_checkpoint's "0 transaction log file(s) added" is extremely misleading  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: log_checkpoint's "0 transaction log file(s) added" is extremely misleading  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On January 22, 2016 3:29:44 AM GMT+01:00, Simon Riggs <simon@2ndQuadrant.com> wrote:
>On 22 January 2016 at 01:12, Andres Freund <andres@anarazel.de> wrote:
>
>> Hi,
>>
>> While in theory correct, I think $subject is basically meaningless
>> because other backends may have added thousands of new segments. Yes,
>it
>> wasn't the checkpointer, but that's not particularly relevant
>> imo. Additionally, afaics, it will only ever be 0 or 1.
>>
>
>Even better, we could make it add >1

That'd indeed be good, but I don't think it really will address my complaint: We'd still potentially create new
segmentsoutside the prealloc call. Including from within the checkpointer, when flushing WAL to be able to write out a
page.

Andres

---
Please excuse brevity and formatting - I am writing this on my mobile phone.



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: log_checkpoint's "0 transaction log file(s) added" is extremely misleading
Next
From: Craig Ringer
Date:
Subject: Re: Re: pglogical_output - a general purpose logical decoding output plugin