Re: libpq compression

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: libpq compression
Date: 2018-06-07 02:22:21
Message-ID: CAMsr+YFkrDWHOTXShFgFA8ekmmsG45KyA-kKXbhbH1DL+mms4g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7 June 2018 at 04:01, 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.
>

Strongly agree. Let libpq handle it first with the core protocol support
and connstr parsing, add convenience flags later.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2018-06-07 02:51:09 Re: why partition pruning doesn't work?
Previous Message Amit Langote 2018-06-07 02:21:33 Re: Remove mention in docs that foreign keys on partitioned tables are not supported