Re: Reword docs of feature "Remove temporary files after backend crash" - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: Reword docs of feature "Remove temporary files after backend crash"
Date
Msg-id CALj2ACVkNHaN9aqUjx3vSXZYaj++1whYU2DsEGhBeMvYDc+odw@mail.gmail.com
Whole thread Raw
In response to Re: Reword docs of feature "Remove temporary files after backend crash"  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: Reword docs of feature "Remove temporary files after backend crash"  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers
On Sat, Oct 9, 2021 at 9:42 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
>
> I doubt there's much confusion here - crashes are treated the same.  I think
> the fix would be to say "server crash" rather than backend crash.

IIUC, the "server crash" includes any backend, auxiliary process,
postmaster crash i.e. database cluster/instance crash. The commit
cd91de0d1 especially added the temp file cleanup support if any
backend or auxiliary process (except syslogger and stats collector)
crashes. The temp file cleanup in postmaster crash does exist prior to
the commit cd91de0d1.

When we add the description about the new GUC introduced by the commit
cd91de0d1, let's be clear as to which crash triggers the new temp file
cleanup path.

Regards,
Bharath Rupireddy.



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: Reword docs of feature "Remove temporary files after backend crash"
Next
From: Tom Lane
Date:
Subject: Add planner support function for starts_with()