| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Idea: closing the loop for "pg_ctl reload" |
| Date: | 2015-03-03 23:13:48 |
| Message-ID: | 1682.1425424428@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> writes:
> On 3/3/15 11:48 AM, Andres Freund wrote:
>> It'll be confusing to have different interfaces in one/multiple error cases.
> If we simply don't want the code complexity then fine, but I just don't
> buy this argument. How could it possibly be confusing?
What I'm concerned about is confusing the code. There is a lot of stuff
that looks at pidfiles and a lot of it is not very bright (note upthread
argument about "cat" vs "head -1"). I don't want possibly localized
(non-ASCII) text in there, especially when there's not going to be any
sane way to know which encoding it's in. And I definitely don't want
multiline error messages in there.
It's possible we could dumb things down enough to meet these restrictions,
but I'd really rather not go there at all.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-03-03 23:22:11 | Re: Proposal: knowing detail of config files via SQL |
| Previous Message | Tom Lane | 2015-03-03 22:58:27 | Re: Proposal: knowing detail of config files via SQL |