From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: tab-completion debug print |
Date: | 2018-12-14 04:55:39 |
Message-ID: | 20181214045539.GP416@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Dec 13, 2018 at 07:43:52PM +0100, Peter Eisentraut wrote:
> On 13/12/2018 12:07, Kyotaro HORIGUCHI wrote:
> > - v6-0002-Add-psql-g-option-to-control-debug-print.patch
> >
> > Applies on top of 0001. Code is always active, -g addition to
> > -L activates debug print into the log file. If only -g is
> > specified it is forcibly turned off.
> >
> > > $ psql postgres -g
> > > psql: no session log file, turn off debug print
> > > psql (12devel)
> > > Type "help" for help.
> >
> > -g option shows in help message. (perhaps arguable.)
>
> I'm not sure that this should be a run-time option.
Given the often onerous givens of installing new software on
production machines, I'm thinking it actually should be.
> But we surely don't want to use up a good short option letter for
> this.
Would it make sense to roll this into the -L option?
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-12-14 05:13:58 | Re: Valgrind failures in Apply Launcher's bgworker_quickdie() exit |
Previous Message | Amit Langote | 2018-12-14 04:22:26 | Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |