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

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, PostgreSQL Hackers <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:59:58
Message-ID: CALj2ACWy5qTxObxjVm_Z_yjJXg1EEbrCvjDSJO8fcx4FGiTYnA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 11, 2021 at 2:53 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
>
> 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.

Thanks.

Regards,
Bharath Rupireddy.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Markus Winand 2021-10-11 10:22:41 Re: EXPLAIN(VERBOSE) to CTE with SEARCH BREADTH FIRST fails
Previous 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