Re: [HACKERS] gitlab post-mortem: pg_basebackup waiting forcheckpoint
От | Jim Nasby |
---|---|
Тема | Re: [HACKERS] gitlab post-mortem: pg_basebackup waiting forcheckpoint |
Дата | |
Msg-id | f444d1a6-fb97-3283-cfb5-b71b77b791b8@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] gitlab post-mortem: pg_basebackup waiting forcheckpoint (Michael Banck <michael.banck@credativ.de>) |
Ответы |
Re: [HACKERS] gitlab post-mortem: pg_basebackup waiting for checkpoint
|
Список | 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)
В списке pgsql-hackers по дате отправления: