Re: gitlab post-mortem: pg_basebackup waiting for checkpoint

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Michael Banck <michael(dot)banck(at)credativ(dot)de>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: gitlab post-mortem: pg_basebackup waiting for checkpoint
Date: 2017-02-15 23:05:28
Message-ID: CAMkU=1wV11t2X6XQgK3G6B5zLGNZ95PsMzVsjsnXhmyP-3hzmA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 14, 2017 at 9:06 AM, Magnus Hagander <magnus(at)hagander(dot)net>
wrote:

Yeah, that's my view as well. I'm all for including it in verbose mode.
>
> *Iff* we can get a progress indicator through the checkpoint we could
> include that in --progress mode. But that's a different patch, of course,
> but it shouldn't be included in the default output even if we find it.
>
>
I think it should show up in --progress mode. It would be great if we
could show fine-grained progress reports on the checkpoint, but if we can't
do that we should still report as fine as we are able to, which is that a
checkpoint is in progress. Otherwise we are setting the perfect as the
enemy of the good.

Cheers,

Jeff

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2017-02-15 23:22:47 Re: WIP: [[Parallel] Shared] Hash
Previous Message Andres Freund 2017-02-15 23:04:31 Re: bytea_output vs make installcheck