Re: [PATCH] Proposal for HIDDEN/INVISIBLE column

From: Gilles Darold <gilles(at)migops(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Proposal for HIDDEN/INVISIBLE column
Date: 2021-10-17 21:01:08
Message-ID: a9150da6-503a-a5a2-a80e-9dedc63287db@migops.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Here is a new version of the patch for the hidden column feature with
the following changes:

  - Rename the HIDDEN into UNEXPANDED and replace all references to
hidden column into unexpanded column

  - Remove changes in the information_schema

  - Limit use of the UNEXPANDED attribute to ALTER COLUMN SET/DROP
commands.

  - Add a check into SET UNEXPANDED code to verify that there is at
least one column expanded.

  - Verify that INSERT INTO table SELECT * FROM table respect the
unexpanded column feature.

  - Verify that RETURNING * clause also respect the unexpanded column
feature.

I have kept the behavior on function using the wildcard * which does not
take care of the unexpanded column attribute.

I have not though of other gotcha for the moment, I will update the
patch if other cases come. In psql the Expended  information is
displayed when using \d+, perhaps it could be better to see this
information directly with \d so that the information comes to the eyes
immediately.

--
Gilles Darold

Attachment Content-Type Size
0001-unexpanded-column-v2.patch text/x-patch 502.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vik Fearing 2021-10-17 21:04:15 Re: [PATCH] Proposal for HIDDEN/INVISIBLE column
Previous Message Alvaro Herrera 2021-10-17 20:05:25 Re: Refactoring pg_dump's getTables()