| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, 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:50:11 |
| Message-ID: | 5D2BB8D3-459E-4768-9E4C-0D16F026FD13@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 24, 2010, at 3:24 PM, Tom Lane wrote:
> 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)));
>
> which now that I look at it could use some wordsmithing itself.
“Bitch, can’t you see that I’m still waiting for the archive to complete? WTF were you thinking? Jesus!”
My $0.02.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-02-24 23:53:45 | Re: pg_stop_backup does not complete |
| Previous Message | Tom Lane | 2010-02-24 23:24:47 | Re: pg_stop_backup does not complete |