| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_stop_backup does not complete |
| Date: | 2010-02-24 23:53:45 |
| Message-ID: | 4B85BC09.1020603@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> If you like the concept, then the next question is exactly how to phrase
> the messages. All we have at the moment is the inside-the-delay-loop
> warning:
>
> ereport(WARNING,
> (errmsg("pg_stop_backup still waiting for archive to complete (%d seconds elapsed)",
> waits)));
Well, we'll want this message first, as soon as pg_stop_backup finishes
checkpointing:
WARNING: Stop backup work complete. Now awaiting completion of WAL
archiving.
Then after 60s:
WARNING: pg_stop_backup is still waiting for WAL archiving to complete
(%d seconds elapsed).
HINT: Check if your WAL archive_command is failing. You may abort
pg_stop_backup at this point, but you will not be able to use the
resulting clone.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-02-24 23:57:53 | Re: pg_stop_backup does not complete |
| Previous Message | David E. Wheeler | 2010-02-24 23:50:11 | Re: pg_stop_backup does not complete |