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: Christoph Berg <myon@debian.org>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Julien Rouhaud <rjuju123@gmail.com>
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 Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: How about a psql backslash command to show GUCs?
Date: Wed, 08 Jun 2022 13:26:50 -0400
Message-ID: <1704674.1654709210@sss.pgh.pa.us> (raw)
In-Reply-To: <8f498b02-f6a9-1544-4cb0-47dc2a5d3ae0@postgresql.org>
References: <9439380b-a81f-c910-f527-db4d470b026b@postgresql.org>
	<531275.1649707882@sss.pgh.pa.us>
	<7bba5a32-65fe-04e1-7c36-efd963a625c9@postgresql.org>
	<807242.1649776780@sss.pgh.pa.us>
	<20220606135529.GV29853@telsasoft.com>
	<918042.1654531335@sss.pgh.pa.us>
	<CA+TgmoZQUHhhrw8ZHAaM0jKdpx+5OP7b3pLwNEFDbk5C0VVpuQ@mail.gmail.com>
	<952350.1654549308@sss.pgh.pa.us>
	<CA+Tgmob12ZKj-S6mnFbBMS7DPuiSHV8H0bd7UP=pXT+BYj8a3Q@mail.gmail.com>
	<29d873fa-ce53-0eeb-ddf5-0a0d38458d16@postgresql.org>
	<Yp9vMaQFGTkkcqDu@msg.df7cb.de>
	<1219250.1654621343@sss.pgh.pa.us>
	<1436476.1654646305@sss.pgh.pa.us>
	<47102fd4-f2c9-40c3-f6dc-0f99d6b6ed6f@postgresql.org>
	<1478411.1654657057@sss.pgh.pa.us>
	<8f498b02-f6a9-1544-4cb0-47dc2a5d3ae0@postgresql.org>

"Jonathan S. Katz" <jkatz@postgresql.org> writes:
> Interesting. OK, I'd say let's keep the behavior that's in the patch.

Pushed then.

			regards, tom lane





view thread (71+ messages)  latest in thread

Message-ID: <1704674.1654709210@sss.pgh.pa.us>
Permalink:  ../1704674.1654709210@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1704674.1654709210@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, myon@debian.org, robertmhaas@gmail.com, pryzby@telsasoft.com, rjuju123@gmail.com, 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: <1704674.1654709210@sss.pgh.pa.us>
  References: <9439380b-a81f-c910-f527-db4d470b026b@postgresql.org> <531275.1649707882@sss.pgh.pa.us> <7bba5a32-65fe-04e1-7c36-efd963a625c9@postgresql.org> <807242.1649776780@sss.pgh.pa.us> <20220606135529.GV29853@telsasoft.com> <918042.1654531335@sss.pgh.pa.us> <CA+TgmoZQUHhhrw8ZHAaM0jKdpx+5OP7b3pLwNEFDbk5C0VVpuQ@mail.gmail.com> <952350.1654549308@sss.pgh.pa.us> <CA+Tgmob12ZKj-S6mnFbBMS7DPuiSHV8H0bd7UP=pXT+BYj8a3Q@mail.gmail.com> <29d873fa-ce53-0eeb-ddf5-0a0d38458d16@postgresql.org> <Yp9vMaQFGTkkcqDu@msg.df7cb.de> <1219250.1654621343@sss.pgh.pa.us> <1436476.1654646305@sss.pgh.pa.us> <47102fd4-f2c9-40c3-f6dc-0f99d6b6ed6f@postgresql.org> <1478411.1654657057@sss.pgh.pa.us> <8f498b02-f6a9-1544-4cb0-47dc2a5d3ae0@postgresql.org> <1704674.1654709210@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