| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(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-26 09:41:26 |
| Message-ID: | 1072A701DD73424B0EE6268C@[172.26.14.62] |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
--On 24. Februar 2010 16:01:02 -0500 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> One objection to this is that it's not very clear to the user when
> pg_stop_backup has finished with actual work and is just waiting for the
> archiver, ie when is it safe to hit control-C? Maybe we should emit a
> "backup done, waiting for archiver to complete" notice before entering
> the sleep loop.
+1 for this. This hint would certainly help to recognize the issue
immediately (or at least point to a possible cause).
--
Thanks
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeroen Vermeulen | 2010-02-26 10:20:17 | Re: Avoiding bad prepared-statement plans. |
| Previous Message | Karl Schnaitter | 2010-02-26 09:27:39 | Re: A thought on Index Organized Tables |