pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Michael Banck <michael.banck@credativ.de>
To: Magnus Hagander <magnus@hagander.net>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: gitlab post-mortem: pg_basebackup waiting for checkpoint
Date: Sun, 12 Feb 2017 20:29:25 -0600
Message-ID: <f444d1a6-fb97-3283-cfb5-b71b77b791b8@BlueTreble.com> (raw)
In-Reply-To: <1486809384.14426.1.camel@credativ.de>
References: <1486805889.24568.96.camel@credativ.de>
	<CABUevExpVYuLUgoNgYNNHxFmZqo3PuuaKgcVwYE5B5wCGScZkQ@mail.gmail.com>
	<1486808720.24568.103.camel@credativ.de>
	<1486809384.14426.1.camel@credativ.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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)


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (30+ messages)  latest in thread

Message-ID: <f444d1a6-fb97-3283-cfb5-b71b77b791b8@BlueTreble.com>
Permalink:  ../f444d1a6-fb97-3283-cfb5-b71b77b791b8@BlueTreble.com/
Also on:    postgresql.org/message-id/f444d1a6-fb97-3283-cfb5-b71b77b791b8@BlueTreble.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: Jim.Nasby@BlueTreble.com, michael.banck@credativ.de, magnus@hagander.net
  Subject: Re: gitlab post-mortem: pg_basebackup waiting for checkpoint
  In-Reply-To: <f444d1a6-fb97-3283-cfb5-b71b77b791b8@BlueTreble.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox