From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, david(at)fetter(dot)org |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: tab-completion debug print |
Date: | 2018-12-13 18:43:52 |
Message-ID: | b78e1fad-5b6c-aa2b-a66d-59f0f9dc8eee@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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. But we surely don't
want to use up a good short option letter for this.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2018-12-13 18:45:30 | Re: Change pgarch_readyXlog() to return .history files first |
Previous Message | Alvaro Herrera | 2018-12-13 17:58:02 | Re: Cache lookup errors with functions manipulation object addresses |