Postgres Pro
Downloads
Home   >   mailing lists

Re: How about a psql backslash command to show GUCs? - Mailing list pgsql-hackers

From Jonathan S. Katz
Subject Re: How about a psql backslash command to show GUCs?
Date
Msg-id b287822f-6c42-e213-dbb1-edcf3e725826@postgresql.org
Whole thread Raw
In response to Re: How about a psql backslash command to show GUCs?  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
Tree view 
On 4/7/22 11:10 AM, David G. Johnston wrote:
> On Thu, Apr 7, 2022 at 7:56 AM Tom Lane <tgl@sss.pgh.pa.us 
> <mailto:tgl@sss.pgh.pa.us>> wrote:
> 
>     "Jonathan S. Katz" <jkatz@postgresql.org
>     <mailto:jkatz@postgresql.org>> writes:
> 
>      > Maybe to appeal to all crowds, we say "list configuration parameters
>      > (GUCs)"?
> 
>     I'm in the camp that says that GUC is not an acronym we wish to expose
>     to end users.
> 
> 
> I am too.

WFM.

Jonathan
Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Add index scan progress to pg_stat_progress_vacuum
Next
From: Tom Lane
Date:
Subject: Re: API stability [was: pgsql: Fix possible recovery trouble if TRUNCATE overlaps a checkpoint.]