libpq compression - Mailing list pgsql-hackers

From David G. Johnston
Subject libpq compression
Date
Msg-id CAKFQuwaTe6=0EVe_5TwGDNKJj0myswxfmH=ktfh_Wf2dOP-DBQ@mail.gmail.com
Whole thread Raw
In response to Re: libpq compression  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Wednesday, June 6, 2018, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
On 6/6/18 13:20, Konstantin Knizhnik wrote:
> Well, psql really allows to specify complete connection string with -d
> options (although it is not mentioned in help).
> But still I think that it is inconvenient to require user to write
> complete connection string to be able to specify compression option,
> while everybody prefer to use -h, -U, -p  options to specify
> correspondent components of connection string.

I recommend that you avoid derailing your effort by hinging it on this
issue.  You can always add command-line options after the libpq support
is in.


It probably requires a long option.  It can be debated whether a short option is warranted (as well as an environment variable).

David J.

pgsql-hackers by date:

Previous
From: Steven Fackler
Date:
Subject: Re: Supporting tls-server-end-point as SCRAM channel binding forOpenSSL 1.0.0 and 1.0.1
Next
From: Peter Eisentraut
Date:
Subject: Re: SCRAM with channel binding downgrade attack