Re: gitlab post-mortem: pg_basebackup waiting for checkpoint

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Michael Banck <michael(dot)banck(at)credativ(dot)de>, Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: gitlab post-mortem: pg_basebackup waiting for checkpoint
Date: 2017-02-13 02:29:25
Message-ID: f444d1a6-fb97-3283-cfb5-b71b77b791b8@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/11/17 4:36 AM, Michael Banck wrote:
> I guess you're right, I've moved it further down. There is in fact a
> message about the xlog location (unless you switch off wal entirely),
> but having another one right before that mentioning the completed
> checkpoint sounds ok to me.

1) I don't think this should be verbose output. Having a program sit
there "doing nothing" for no apparent reason is just horrible UI design.

2) I think it'd be useful to have a way to get the status of a running
checkpoint. The checkpointer already has that info, and I think it might
even be in shared memory already. If there was a function that reported
checkpoint status pg_basebackup could poll that to provide users with
live status. That should be a separate patch though.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2017-02-13 02:41:55 Re: Checksums by default?
Previous Message Jim Nasby 2017-02-13 02:20:34 Re: log_autovacuum_min_duration doesn't log VACUUMs