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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Justin Pryzby <pryzby(at)telsasoft(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: 2022-04-04 12:29:40
Message-ID: F2BF73DA-2743-45BC-A3FB-11D3F03A0C94@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 1 Apr 2022, at 15:57, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Apr 1, 2022 at 9:42 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:

>> This has been sitting the CF for quite some time, time to make a decision on
>> it. I think it makes sense, having detailed docs around debugging is rarely a
>> bad thing. Does anyone else have opinions?
>
> I don't like it. It seems to me that it will result in a lot of
> duplication in the docs, because every time we talk about something
> that happens in connection with a crash, we'll need to talk about this
> same list of exceptions.

Fair enough, that's a valid concern. Unless others object I then think we
should close this patch in the CF as rejected.

--
Daniel Gustafsson https://vmware.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2022-04-04 12:55:54 Re: generic plans and "initial" pruning
Previous Message Amit Kapila 2022-04-04 11:45:36 Re: logical decoding and replication of sequences