| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
| Cc: | "Iwata, Aya" <iwata(dot)aya(at)jp(dot)fujitsu(dot)com>, 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 09:33:04 |
| Message-ID: | A72D525A-5DB2-41E2-98E8-25CC6649AC1E@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 8 Feb 2019, at 10:15, Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> wrote:
> Frankly speaking, I do not think that such flexibility in choosing compression algorithms is really needed.
> I do not expect that there will be many situations where old client has to communicate with new server or visa versa.
> In most cases both client and server belongs to the same postgres distributive and so implements the same compression algorithm.
> As far as we are compressing only temporary data (traffic), the problem of providing backward compatibility seems to be not so important.
I don’t think this assumption is entirely valid, and would risk unnecessary
breakage.
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-02-08 09:35:03 | Re: ON SELECT rule on a table without columns |
| Previous Message | David Rowley | 2019-02-08 09:27:59 | Re: speeding up planning with partitions |