| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Minor typo |
| Date: | 2018-11-28 00:31:04 |
| Message-ID: | 20181128003104.GR1716@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 27, 2018 at 07:18:39PM -0500, Tom Lane wrote:
> * When wal_compression is enabled and a "hole" is removed from a full
> * page image, the page image is compressed using PGLZ compression.
>
> (BTW, is this trying to say that we don't apply compression if the page
> contains no hole? If so, why not?)
Compression can be applied on a page with or without a hole. What this
sentence means is that the equivalent of a double level of compression
can be applied on top of the hole being removed, if the hole can be
removed.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2018-11-28 00:44:02 | Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 |
| Previous Message | Tom Lane | 2018-11-28 00:18:39 | Re: Minor typo |