From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql ignores failure to open -o target file |
Date: | 2015-12-02 18:31:11 |
Message-ID: | CA+TgmoZOn+guSxe4e+j1aNeyErUQByCuGb2+MO2NBq1PjpD=-Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 2, 2015 at 1:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
>> On Wed, Dec 2, 2015 at 11:04 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>> On Wed, Dec 2, 2015 at 11:07 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>> This seems surprising to me: any other program in the world would do
>>>> exit(1) after discovering that it couldn't write where it had been
>>>> told to. Should we change this?
>
>>> I assume this is a rhetorical question.
>
>> How about this one: do we change this behavior in the back branches?
>
> I don't think we should change this in stable branches. I would vote
> for fixing it in 9.5, though, mainly because the fix is going to interact
> with the extended-mode-wrap fixes I'm also working on.
Oh. I would assume this was an obvious back-patch back to the stone
age. It seems like flagrant bug. Let's revive 7.4 just to fix this.
:-)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-12-02 18:33:28 | Re: [PROPOSAL] VACUUM Progress Checker. |
Previous Message | Tom Lane | 2015-12-02 18:24:49 | Re: psql ignores failure to open -o target file |