| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Marc Mamin <M(dot)Mamin(at)intershop(dot)de>, 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 01:50:42 |
| Message-ID: | 19955.1437789042@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
I don't think we realized that we were changing the default behavior.
Still, it's clearly a bug fix, so I'm disinclined to revert it now.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-07-25 02:22:14 | Re: MultiXact member wraparound protections are now enabled |
| Previous Message | dinesh kumar | 2015-07-25 01:38:53 | Re: Proposing COPY .. WITH PERMISSIVE |