| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: archive_command failures report confusing exit status |
| Date: | 2007-12-11 23:08:20 |
| Message-ID: | 1197414500.4255.1458.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2007-12-11 at 23:31 +0100, Peter Eisentraut wrote:
> Simon Riggs wrote:
> > I prefer archive_command = ... for the errdetail though. The commands
> > can be quite long so the extra words don't really add anything, plus
> > they require translation.
>
> I did like this suggestion, but then I noticed, we don't actually report the
> setting of the archive_command setting but the actual command that was
> executed, with the placeholders filled out. So I think the way I posted it
> is more correct.
I think you should lose the "The", if nothing else. Most Postgres
messages I recall say "return code = xx" not "The return code ..."
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-12-11 23:14:44 | Re: archive_command failures report confusing exit status |
| Previous Message | Simon Riggs | 2007-12-11 23:00:30 | Re: WORM and Read Only Tables (v0.1) |