Re: log_checkpoint's "0 transaction log file(s) added" is extremely misleading

From: Andres Freund <andres(at)anarazel(dot)de>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: log_checkpoint's "0 transaction log file(s) added" is extremely misleading
Date: 2016-01-22 02:33:17
Message-ID: 55E92D09-EB40-4CC0-B6BD-1A7E6B276D84@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On January 22, 2016 3:29:44 AM GMT+01:00, Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:
>On 22 January 2016 at 01:12, Andres Freund <andres(at)anarazel(dot)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 segments outside 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2016-01-22 03:06:03 Re: Re: pglogical_output - a general purpose logical decoding output plugin
Previous Message Simon Riggs 2016-01-22 02:29:44 Re: log_checkpoint's "0 transaction log file(s) added" is extremely misleading