Re: Modify SHOW to display reloptions by accepting table-qualified names.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Modify SHOW to display reloptions by accepting table-qualified names.
Date: 2025-03-24 15:58:56
Message-ID: 1004704.1742831936@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> In discussing vacuum_truncate_set it occurs to me there is no SQL way for
> someone to easily view the current setting (or unset status) of a
> reloption. Seems like we could modify SHOW to cover this use case.

That seems like a pretty awful idea; for starters, there is nothing
preventing overlap between the set of GUC names and the set of
table names.

Perhaps it is worth inventing bespoke syntax for this --- I doubt it,
but others might think differently --- but please let's not overload
SHOW.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2025-03-24 16:00:51 Re: vacuum_truncate configuration parameter and isset_offset
Previous Message Fujii Masao 2025-03-24 15:56:34 Re: pg_recvlogical requires -d but not described on the documentation