pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jonathan S. Katz <jkatz@postgresql.org>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: Christoph Berg <myon@debian.org>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: Joe Conway <mail@joeconway.com>
Cc: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: David Rowley <dgrowleyml@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Subject: Re: How about a psql backslash command to show GUCs?
Date: Sat, 09 Apr 2022 12:27:12 -0400
Message-ID: <4115803.1649521632@sss.pgh.pa.us> (raw)
In-Reply-To: <afad841b-cc31-1784-84f7-b6c3c71d0c5d@postgresql.org>
References: <FF230C05-B27A-4C7B-8514-A5A21EA3D7CC@enterprisedb.com>
	<3370142.1649348973@sss.pgh.pa.us>
	<2DB6EB50-04DF-49D1-BB5B-61C62898BB35@enterprisedb.com>
	<3370992.1649349445@sss.pgh.pa.us>
	<711e43b9-6499-6a8b-0802-fb549874658e@joeconway.com>
	<CAKFQuwb6Ju1VM+hOV2hEbSzoW40o33qp12CQUGRhS+js=vYaew@mail.gmail.com>
	<CAFj8pRA2aEY+SRjZ_WurB8512Etry3Arefv_L7fkpHW-ct3kkQ@mail.gmail.com>
	<3400691.1649363759@sss.pgh.pa.us>
	<YlFQLzlPi4QD0wSi@msg.df7cb.de>
	<4105551.1649514677@sss.pgh.pa.us>
	<YlGtICTMIJ886Ij3@jrouhaud>
	<afad841b-cc31-1784-84f7-b6c3c71d0c5d@postgresql.org>

"Jonathan S. Katz" <jkatz@postgresql.org> writes:
> -1, at least for the moment. Sometimes a user doesn't know what they're 
> looking for coupled with being unaware of what the default value is. If 
> a setting is set to a default value and that value is the problematic 
> setting, a user should be able to see that even in a full list.

Sure, but then you do "\dconfig *".  With there being several hundred
GUCs (and no doubt more coming), I'm not sure that "show me every GUC"
is a common use-case at all, let alone so common as to deserve being
the default behavior.

One thing we could perhaps do to reduce confusion is to change the
table heading when doing this, say from "List of configuration parameters"
to "List of non-default configuration parameters".

			regards, tom lane





view thread (71+ messages)  latest in thread

Message-ID: <4115803.1649521632@sss.pgh.pa.us>
Permalink:  ../4115803.1649521632@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/4115803.1649521632@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jkatz@postgresql.org, rjuju123@gmail.com, myon@debian.org, pavel.stehule@gmail.com, david.g.johnston@gmail.com, mail@joeconway.com, mark.dilger@enterprisedb.com, andrew@dunslane.net, dgrowleyml@gmail.com, alvherre@alvh.no-ip.org
  Subject: Re: How about a psql backslash command to show GUCs?
  In-Reply-To: <4115803.1649521632@sss.pgh.pa.us>
  References: <FF230C05-B27A-4C7B-8514-A5A21EA3D7CC@enterprisedb.com> <3370142.1649348973@sss.pgh.pa.us> <2DB6EB50-04DF-49D1-BB5B-61C62898BB35@enterprisedb.com> <3370992.1649349445@sss.pgh.pa.us> <711e43b9-6499-6a8b-0802-fb549874658e@joeconway.com> <CAKFQuwb6Ju1VM+hOV2hEbSzoW40o33qp12CQUGRhS+js=vYaew@mail.gmail.com> <CAFj8pRA2aEY+SRjZ_WurB8512Etry3Arefv_L7fkpHW-ct3kkQ@mail.gmail.com> <3400691.1649363759@sss.pgh.pa.us> <YlFQLzlPi4QD0wSi@msg.df7cb.de> <4105551.1649514677@sss.pgh.pa.us> <YlGtICTMIJ886Ij3@jrouhaud> <afad841b-cc31-1784-84f7-b6c3c71d0c5d@postgresql.org> <4115803.1649521632@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox