| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Lakshmi N <lakshmin(dot)jhs(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "dean(dot)a(dot)rasheed(at)gmail(dot)com" <dean(dot)a(dot)rasheed(at)gmail(dot)com>, "peter(at)eisentraut(dot)org" <peter(at)eisentraut(dot)org> |
| Subject: | Re: Show VIRTUAL keyword for virtual generated columns in pg_dump and psql |
| Date: | 2026-04-13 12:27:06 |
| Message-ID: | CAKFQuwan3J1WdqtiXr4u9Lmj+5Z7r+hYOKfy_A1g23_8f90LWw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Monday, April 13, 2026, Lakshmi N <lakshmin(dot)jhs(at)gmail(dot)com> wrote:
>
> pg_dump and psql's \d currently display stored and virtual generated
> columns asymmetrically:
>
>
> s_total integer GENERATED ALWAYS AS ((a + b)) STORED
> v_total integer GENERATED ALWAYS AS ((a + b))
>
> Since VIRTUAL is default most likely this was omitted but with this
>
puts the burden on the reader to identify whether it is STORED or
> VIRTUAL since both kinds coexist in v19.
>
The output follows existing conventions of not printing extraneous text.
Additionally, storage itself is non-standard so the absence of a modifier
is producing standard-compliant output. I would -1 changing pg_dump on
this basis. I’d be inclined to go with the symmetry/readability argument
for psql \d though.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Soumya S Murali | 2026-04-13 12:36:03 | Re: Fix bug with accessing to temporary tables of other sessions |
| Previous Message | David Steele | 2026-04-13 11:53:39 | Re: Heads Up: cirrus-ci is shutting down June 1st |