Re: Flexible pglz_stategy values and delete const.

2020-02-17 Thread Moon, Insung
Hello. On Tue, Feb 18, 2020 at 1:20 PM Michael Paquier wrote: > > On Mon, Feb 17, 2020 at 11:04:47AM +0900, Moon, Insung wrote: > > The compression-related strategy is applied only when compressed. > > Decompression does not use strategy, so the old compressed data is not > > affected by the new

Re: Flexible pglz_stategy values and delete const.

2020-02-17 Thread Michael Paquier
On Mon, Feb 17, 2020 at 11:04:47AM +0900, Moon, Insung wrote: > The compression-related strategy is applied only when compressed. > Decompression does not use strategy, so the old compressed data is not > affected by the new patch. This may be a difficult question, but do you have examples of

Flexible pglz_stategy values and delete const.

2020-02-16 Thread Moon, Insung
Dear Hackers. For the current PostgreSQL, the toast data and some WAL data (page data) are compressed using the LZ-based algorithm. For PostgreSQL, two types of strategy(PGLZ_strategy_default, PGLZ_strategy_always) are provided by default, and only used of PGLZ_strategy_default(default values) on