From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_stop_backup does not complete |
Date: | 2010-02-25 17:29:44 |
Message-ID: | 4B86B388.308@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> In an ideal world it would be best if pg_stop_backup could actually
> print the error status of the archiving command.
Agreed.
> And do we have closure on whether a "fast" shutdown is hanging? Or was
> that actually a smart shutdown?
No, I need to retest and verify 100% that the issue wasn't something
other than stop_backup.
> Perhaps "smart" shutdown needs to print out what it's waiting on
> periodically as well, and suggest a fast shutdown to abort those
> transactions.
That would be a good thing to have for PostgreSQL in general. Given
that any number of things can stop a smart shutdown, it's more than a
little baffling to users why one hangs forever.
BUT ... since most users run smart shutdown via a services script,
output on what shutdown is waiting on would need to be written to the
log rather than given interactively.
--Josh Berkus
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2010-02-25 17:31:55 | Re: pg_stop_backup does not complete |
Previous Message | Richard Huxton | 2010-02-25 17:14:33 | Re: plperl.on_init - bug or just me? |