Josh Berkus wrote:
> Currently, if archive_command is failing, pg_stop_backup() will hang
> forever. The only way to figure out what's wrong with pg_stop_backup()
> is to tail the PostgreSQL logs. This is difficult for users to
> troubleshoot, and strongly resists any kind of automation.
That
Hackers,
Since Gabrielle has improved archiving with pg_stat_archiver in 9.4, I'd
like to go further and improve the usability of pg_stop_backup().
However, based on my IRC discussion with Vik, there might not be
consensus on what the right behavior *should* be. This is for 9.5, of
course.
Curre
