Re: libpq compression - Mailing list pgsql-hackers

From Konstantin Knizhnik
Subject Re: libpq compression
Date
Msg-id c5421f2e-918a-2e74-f91a-a951d49012c4@postgrespro.ru
Whole thread Raw
In response to Re: libpq compression  (David Steele <david@pgmasters.net>)
List pgsql-hackers

On 25.03.2019 13:38, David Steele wrote:
> On 3/25/19 1:04 PM, Konstantin Knizhnik wrote:
>>
>>
>> On 25.03.2019 11:06, David Steele wrote:
>>> Konstantin,
>>>
>>>
>>> This patch appears to be failing tests so I have marked it Waiting 
>>> on Author.
>>>
>>> I have also removed the reviewer since no review had been done. 
>>> Maybe somebody else will have a look.
>>>
>>> Regards,
>>
>> Can you please inform me which tests are failed?
>> I have done "make check-world" and there were no failed tests.
>> Actually if compression is not enabled (and it is disabled by default 
>> unless explicitly requested by client), there should be no difference 
>> with vanilla Postgres.
>> So it will be strange if some tests are failed without using 
>> compression.
>
> Check out the cfbot report at http://commitfest.cputube.org.  Both 
> platforms were failed earlier but Windows is running again now. Doubt 
> that will make much difference, though.
>
> Regards,

Yet another version of the patch which should fix problems at Windows.

-- 
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company


Attachment

pgsql-hackers by date:

Previous
From: "Tsunakawa, Takayuki"
Date:
Subject: RE: Re: reloption to prevent VACUUM from truncating empty pages atthe end of relation
Next
From: Michael Paquier
Date:
Subject: Re: pg_malloc0() instead of pg_malloc()+memset()