| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | "Iwata, Aya" <iwata(dot)aya(at)jp(dot)fujitsu(dot)com> |
| Cc: | 'Konstantin Knizhnik' <k(dot)knizhnik(at)postgrespro(dot)ru>, Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "rharwood(at)redhat(dot)com" <rharwood(at)redhat(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, "g(dot)smolkin(at)postgrespro(dot)ru" <g(dot)smolkin(at)postgrespro(dot)ru>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, 'Dmitry Dolgov' <9erthalion6(at)gmail(dot)com> |
| Subject: | Re: libpq compression |
| Date: | 2019-02-08 07:08:28 |
| Message-ID: | 20190208070828.lktk4guf4ebsoyhu@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2019-02-08 07:01:01 +0000, Iwata, Aya wrote:
> > I still not sure whether it is good idea to make it possible to user to
> > explicitly specify compression algorithm.
> > Right now used streaming compression algorithm is hardcoded and depends on
> > --use-zstd ort --use-zlib configuration options.
> > If client and server were built with the same options, then they are able
> > to use compression.
> I understand that compression algorithm is hardcoded in your proposal.
> However given the possibility of future implementation, I think
> it would be better for it to have a flexibility to choose compression library.
Agreed. I think that's a hard requirement. Making explicitly not forward
compatible interfaces is a bad idea.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rushabh Lathia | 2019-02-08 07:11:23 | Re: ON SELECT rule on a table without columns |
| Previous Message | Iwata, Aya | 2019-02-08 07:01:01 | RE: libpq compression |