| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | libpq compression |
| Date: | 2018-06-06 20:16:36 |
| Message-ID: | CAKFQuwaTe6=0EVe_5TwGDNKJj0myswxfmH=ktfh_Wf2dOP-DBQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wednesday, June 6, 2018, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2018-06-06 20:20:24 | Re: SCRAM with channel binding downgrade attack |
| Previous Message | Steven Fackler | 2018-06-06 20:16:11 | Re: Supporting tls-server-end-point as SCRAM channel binding for OpenSSL 1.0.0 and 1.0.1 |