Re: How about a psql backslash command to show GUCs?

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christoph Berg <myon(at)debian(dot)org>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, David Rowley <dgrowleyml(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: How about a psql backslash command to show GUCs?
Date: 2022-04-09 16:50:52
Message-ID: 7e8ae81a-177e-bf71-086d-f460796f5932@postgresfriends.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4/9/22 16:31, Tom Lane wrote:
> Christoph Berg <myon(at)debian(dot)org> writes:
>
>> I would think that if \dconfig showed the non-default settings only,
>> it would be much more useful; the full list would still be available
>> with "\dconfig *". This is in line with \dt only showing tables on the
>> search_path, and "\dt *.*" showing all.
>
> Hm, I could get on board with that -- any other opinions?

+1
--
Vik Fearing

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-04-09 16:51:03 Re: why pg_walfile_name() cannot be executed during recovery?
Previous Message Robert Haas 2022-04-09 16:50:23 Re: How about a psql backslash command to show GUCs?