| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Marc Mamin <M(dot)Mamin(at)intershop(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, "'michael(dot)paquier(at)gmail(dot)com'" <michael(dot)paquier(at)gmail(dot)com> |
| Subject: | Re: pg_dump -Fd and compression level |
| Date: | 2015-07-25 12:56:02 |
| Message-ID: | 55B38762.5080208@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/25/2015 03:20 AM, Andrew Dunstan wrote:
>
> On 07/25/2015 02:34 AM, Marc Mamin wrote:
>>
>>> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>>> Hmm. Yeah. It looks like commit
>>>> a7ad5cf0cfcfab8418000d652fa4f0c6ad6c8911
>>>> changed from using the default compression for libz to using the
>>>> compression set in pg_dump options, which defaults to 0. This actually
>>>> seems like the right thing to do, but it certainly should have been
>>>> called out much more forcefully in release notes, and arguably should
>>>> not have been changed in stable releases. Not sure what we do about
>>>> it now.
>> really 0? wouldn't that mean no compression at all?
>
> No, that's not right either. The default should be
> Z_DEFAULT_COMPRESSION, so we shouldn't actually see a difference in
> the default case. And it is definitely compressing some. So I'm now
> puzzled by what you're seeing.
>
>
OK, I have got this worked out. I'll have a bug fix shortly.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-07-25 13:14:05 | Re: pg_dump -Fd and compression level |
| Previous Message | Michael Paquier | 2015-07-25 12:42:13 | Re: Supporting TAP tests with MSVC and Windows |