| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_stop_backup does not complete |
| Date: | 2010-02-25 02:01:49 |
| Message-ID: | 4B85DA0D.7040103@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/24/10 5:58 PM, Greg Smith wrote:
>
> I though about that for a minute, but didn't think pg_stop_backup is a
> common enough operation that anyone will complain that it's a little
> more verbose in its logging now. I know when I was new to this, I used
> to wonder just what it was busy doing just after executing this command
> when it hung there for a while sometimes, and would have welcomed this
> extra bit of detail--preferably immediately, not even after a 5 or 10
> second delay.
+1
--Josh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2010-02-25 02:07:30 | Re: pg_stop_backup does not complete |
| Previous Message | Greg Smith | 2010-02-25 01:58:27 | Re: pg_stop_backup does not complete |