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

From John Naylor
Subject Re: cutting down the TODO list thread
Date
Msg-id CAFBsxsFqAv=TFc+riJKuVX_-tf8QDqXqNtpMVKu_MBiGjEcvQA@mail.gmail.com
Whole thread Raw
In response to Re: cutting down the TODO list thread  (Bruce Momjian <bruce@momjian.us>)
Responses Re: cutting down the TODO list thread  (John Naylor <john.naylor@enterprisedb.com>)
List pgsql-hackers

On Mon, Jan 30, 2023 at 10:07 PM Bruce Momjian <bruce@momjian.us> wrote:
>
> On Mon, Jan 30, 2023 at 01:13:45PM +0700, John Naylor wrote:

> > "It's worth checking if the feature of interest is found in the TODO list on
> > our wiki: http://wiki.postgresql.org/wiki/TODO. The entries there often have
> > additional information about the feature and may point to reasons why it hasn't
> > been implemented yet."
>
> Good.

> > Do I understand right that we could just remove this entire section "What areas
> > need work?"?
>
> Yes, I think so.

> > > I can now see that just removing the [E] label totally is the right
> > > answer.  Yes, there might be an easy item on there, but the fact we have
> > > three labeled and they are not easy makes me thing [E] is causing more
> > > problems than it solves.
> >
> > Okay, having heard no objections I'll remove it.

These are all done now.

I'll try to get back to culling the list items at the end of April.

--
John Naylor
EDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Add progress reporting to pg_verifybackup
Next
From: Amit Kapila
Date:
Subject: Re: Exit walsender before confirming remote flush in logical replication