Re: pgsql/ oc/src/sgml/release.sgml rc/backend/com ... - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql/ oc/src/sgml/release.sgml rc/backend/com ...
Date
Msg-id 12702.1027193162@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql/ oc/src/sgml/release.sgml rc/backend/com ...  (Joe Conway <mail@joeconway.com>)
List pgsql-committers
Joe Conway <mail@joeconway.com> writes:
> I do think that it is conceivable that we want to be able to suppress
> the examination of some settings, but I would think that would apply to
> SHOW just the same as SHOW ALL. It seems that anything I can SHOW should
> be there when I do SHOW ALL. Maybe it should be GUC_NO_SHOW and apply to
> both?

Nah, that can be implemented by the show_hook subroutine refusing to
disclose anything.  NO_SHOW_ALL is only useful for making SHOW ALL
vary from what SHOW does.

            regards, tom lane

pgsql-committers by date:

Previous
From: Joe Conway
Date:
Subject: Re: pgsql/ oc/src/sgml/release.sgml rc/backend/com ...
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql/src/backend/commands trigger.c