Re: [PATCH] SQL function to report log message - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: [PATCH] SQL function to report log message
Date
Msg-id CAMkU=1yFpQN==fiDT-y9JOm1PF-cgNmFnkRGUWbipfErB5QpNA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] SQL function to report log message  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [PATCH] SQL function to report log message  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Thu, Sep 10, 2015 at 8:14 AM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
dinesh kumar wrote:

> Also, I was under impression that, all our TODO
> <https://wiki.postgresql.org/wiki/Todo> items are filtered for the real use
> cases. Is my impression wrong. If I wanted to work on another TODO item,
> where i need to take a look.

Your impression is completely, absolutely, horribly wrong.

The TODO contains some ideas that are good but postponed, other ideas
that are bad but we didn't know at the time they were recorded, other
ideas that we don't know either way.  Before doing anything on an item
from the TODO list, you should first read the linked threads (if any),
and keep track when they end with an email saying "what an awful idea".
If this doesn't happen, _search_ for other threads not linked on the
TODO list that also deal with the same topic; note if they end the same
way (if you find such threads, it's useful to add a link to them in the
TODO item).

Even if you can't find overly negative opinions about some item, discuss
it here before doing any actual coding.

I wonder if we need a new page TONOTDO or something like that.


The bottom of the TODO list already has "Features We Do Not Want".  I think it would just be a matter of moving them down to that section.

Or maybe a new section of "Features I lost an argument over, but hope to eventually accumulate enough allies to re-fight that battle".

I've thought in the paste that maybe we should create a "stale" badge and go through and add it to every open item.  Once someone has re-evaluated that it is still desirable (and that the description even makes sense in the first place), they can remove the stale badge.  Currently, the TODO seems to be a collection of belly button lint more than anything else.

Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Use pg_rewind when target timeline was switched
Next
From: Robert Haas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file