Re: Things I don't like about \du's "Attributes" column - Mailing list pgsql-hackers

From Pavel Luzanov
Subject Re: Things I don't like about \du's "Attributes" column
Date
Msg-id 1b9df82b-2261-4156-83d4-fd8648985232@postgrespro.ru
Whole thread Raw
In response to Re: Things I don't like about \du's "Attributes" column  (Pavel Luzanov <p.luzanov@postgrespro.ru>)
List pgsql-hackers
Hello,
After reading thread "new commitfest transition guidance"[0],
and as patch author, I decided to write short summary for this
committfest entry[1].

Last patch has version 8, example output and code are here[2].
Proposed approach to \du command has not found positive responses
for several months. From this point of view the commitfest entry can be
closed (Returned with feedback/Rejected - not sure).

But Robert suggested to think about \du output in another direction[3].
I find it very interesting, but I haven't had time to try it.
And I know for sure that I won't be able to find time until the summer.

I don't understand from new commitfest transition guidance
what to do with status of commitfest entry in this case.
May be it needs to be closed. And in a case I will be able to propose
a new version, I will open a new entry.

The commitfest entry now has Needs Review status and stayed in
the closed January commitfest.

0. https://www.postgresql.org/message-id/flat/003e3a66-8fcc-4ca0-9e0e-c0afda1c9424%40eisentraut.org
1. https://commitfest.postgresql.org/51/4738/
2. https://www.postgresql.org/message-id/5341835b-e7be-44dc-b6e5-400e9e3f3c64@postgrespro.ru
3. https://www.postgresql.org/message-id/CA%2BTgmoZ_uGDb3N8AKHG6nOc5HZPp5Y_ogFhrRbhoVnPHN%2B4t3g%40mail.gmail.com

pgsql-hackers by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: Virtual generated columns
Next
From: Zhang Mingli
Date:
Subject: Re: Virtual generated columns