| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
| Cc: | Rambabu V <ram(dot)wissen(at)gmail(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Need Help on wal_compression |
| Date: | 2018-01-10 01:24:10 |
| Message-ID: | 20180110012410.GD336@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Jan 09, 2018 at 01:53:14PM -0300, Claudio Freire wrote:
> That shows 50% of that are full page writes. This is with compression
> enabled. WAL compression will only help FPW, so if you don't have a large
> volume of FPW, or they don't compress well, you won't benefit much.
This highly depends on the data types used as well. You won't get much
compressibility with things like UUIDs for example. When we worked on
the patch, I recall that FDW compression saved 25% for a relation with a
one-column integer, and only 12~15% when using UUIDs.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Danylo Hlynskyi | 2018-01-10 03:29:12 | RE: Performance of a Query |
| Previous Message | Scott Marlowe | 2018-01-09 23:25:58 | Re: Performance of a Query |