| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Incorrect errno used with %m for backend code |
| Date: | 2018-06-22 19:14:06 |
| Message-ID: | 20180622191406.3f4ykhdfpoqozgu3@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2018-06-22 11:15:53 -0400, Alvaro Herrera wrote:
> I don't understand the logic in RestoreSlotFromDisk that fsync the file
> prior to reading it. What are we protecting against?
we could previously have crashed before fsyncing. But we can only rely
on slot contents being durable if we fsync them. Therefore we fsync
before reading, after a crash.
> Anyway, while I think it would be nice to have CloseTransientFile
> restore the original errno if there was one and close goes well, it
> probably unduly complicates its API contract.
Yea, agreed.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | sixela | 2018-06-22 19:20:13 | Re: pg_verify_checksums review |
| Previous Message | Andres Freund | 2018-06-22 19:11:30 | Re: [PATCH] Include application_name in "connection authorized" log message |