Re: Reword docs of feature "Remove temporary files after backend crash"

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Euler Taveira <euler(at)eulerto(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Subject: Re: Reword docs of feature "Remove temporary files after backend crash"
Date: 2021-10-11 09:23:50
Message-ID: 20211011092350.GV27491@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 11, 2021 at 12:50:28PM +0530, Bharath Rupireddy wrote:
> I noticed another thing that the remove_temp_files_after_crash is
> categorized as DEVELOPER_OPTIONS, shouldn't it be under
> RESOURCES_DISK?

See here:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=797b0fc0b078c7b4c46ef9f2d9e47aa2d98c6c63

The old behavior of leaving the tempfiles behind isn't expected to be useful to
uses, and the only reason to keep them was to allow debugging.

Putting it in DEVELOPER means that it's not in the user-facing
postgresql.conf.sample.

--
Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Drouvot, Bertrand 2021-10-11 09:44:21 Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns
Previous Message Sasasu 2021-10-11 08:34:21 Re: storing an explicit nonce