| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: libpq compression |
| Date: | 2018-06-06 20:01:32 |
| Message-ID: | ea1a4a27-2bb1-5406-f29d-b17b77fcf7cd@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2018-06-06 20:11:36 | Re: Spilling hashed SetOps and aggregates to disk |
| Previous Message | Peter Eisentraut | 2018-06-06 19:46:52 | Re: Transform for pl/perl |