Re: tab-completion debug print - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: tab-completion debug print
Date
Msg-id b78e1fad-5b6c-aa2b-a66d-59f0f9dc8eee@2ndquadrant.com
Whole thread Raw
In response to Re: tab-completion debug print  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: tab-completion debug print  (David Fetter <david@fetter.org>)
List 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


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Cache lookup errors with functions manipulation object addresses
Next
From: David Steele
Date:
Subject: Re: Change pgarch_readyXlog() to return .history files first