Re: TODO list (was Re: Contributing with code) - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: TODO list (was Re: Contributing with code)
Date
Msg-id 20180103161005.2qpm6bc7t3u2ad36@alvherre.pgsql
Whole thread Raw
In response to Re: TODO list (was Re: Contributing with code)  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: TODO list (was Re: Contributing with code)
List pgsql-hackers
I think deleting the TODO list is a bad idea -- it contains very useful
pointers to previous discussion on hard topics.  

Jeff Janes wrote:
> On Tue, Jan 2, 2018 at 2:48 PM, Robert Haas <robertmhaas@gmail.com> wrote:

> > It also has a note at the top saying we think it's complete, but we
> > don't think that, or I don't think it anyway.
> 
> Yeah, I don't care for that, either.

This text was added by [1] as saying:
    > This list contains '''some known PostgreSQL bugs and feature
    > requests''' and we hope it contains all such
(before this, it said "all known Pg bugs" which seemed too optimistic,
so the correction was in a good direction) and later amended by [2] to
the current wording ("This list contains '''known PostgreSQL bugs and
feature requests''' and we hope it is complete").  I think [1]'s wording
was okay, but the other one not so much.

I rewrote the text.  I thought about presenting my draft here first, but
hey, it's a wiki.

[1] https://wiki.postgresql.org/index.php?title=Todo&diff=17840&oldid=17669
[2] https://wiki.postgresql.org/index.php?title=Todo&diff=17961&oldid=17877

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: [HACKERS] SQL/JSON in PostgreSQL
Next
From: Fabien COELHO
Date:
Subject: Re: WIP Patch: Pgbench Serialization and deadlock errors