Re: cutting down the TODO list thread - Mailing list pgsql-hackers

From Matthias van de Meent
Subject Re: cutting down the TODO list thread
Date
Msg-id CAEze2Whz2bwnxBVOwuXZHZo10srvTEPs2-OwFvA5a=AahTwVQg@mail.gmail.com
Whole thread Raw
In response to Re: cutting down the TODO list thread  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: cutting down the TODO list thread  (John Naylor <john.naylor@enterprisedb.com>)
List pgsql-hackers
On Tue, 16 May 2023 at 14:27, Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Tue, May 16, 2023 at 8:18 AM Matthias van de Meent
> <boekewurm+postgres@gmail.com> wrote:
> > Agreed; and that's why I'm not against removing the specific wording
> > of the item. This may not have been clearly described in my previous
> > mail, but I would instead like to see a TODO list item which covers
> > the need to improve the number of cases where we provide actionable
> > advice, and specifically those cases where there is not One Obvious
> > Issue (OOI;s like when getting close to wraparound; or close
> > checkpoints, or ...).
>
> My vote is for just removing the item, rather than putting it on the
> not wanted list. I don't think it's useful to put things as general as
> what you say here on the list. But putting this item in the not wanted
> section might imply that it's not an area we're looking to improve,
> which as you say, is false.

That makes sense. Agreed.


Kind regards,

Matthias van de Meent



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Assert failure of the cross-check for nullingrels
Next
From: Jehan-Guillaume de Rorthais
Date:
Subject: Re: Memory leak from ExecutorState context?