| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Robbie Harwood <rharwood(at)redhat(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, hlinnaka <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: Fix some error handling for read() and errno |
| Date: | 2018-06-22 23:48:03 |
| Message-ID: | 20180622234803.GA1134@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 22, 2018 at 09:51:30AM -0400, Alvaro Herrera wrote:
> On 2018-Jun-22, Robert Haas wrote:
>> I think this should be split into two patches. Fixing failure to save
>> and restore errno is a different issue from cleaning up short write
>> messages. I agree that the former should be back-patched and the
>> latter not.
>
> Hmm, yeah, good thought, +1.
That's exactly why I have started this thread so as both problems are
addressed separately:
https://www.postgresql.org/message-id/20180622061535.GD5215@paquier.xyz
And back-patching the errno patch while only bothering about messages on
HEAD matches also what I got in mind. I'll come back to this thread
once the errno issues are all addressed.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haribabu Kommi | 2018-06-23 02:06:39 | Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query |
| Previous Message | Nikita Glukhov | 2018-06-22 23:44:29 | Re: Jsonb transform for pl/python |