Re: Flexible pglz_stategy values and delete const.

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "Moon, Insung" <tsukiwamoon(dot)pgsql(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Flexible pglz_stategy values and delete const.
Date: 2020-02-18 04:20:41
Message-ID: 20200218042041.GE4176@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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
workloads which could benefit of having such reloptions? It is not
the kind of options which are easy to tune, still a POC should be
simple enough to implement to show your point.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-02-18 04:28:36 Re: LOCK TABLE and DROP TABLE on temp tables of other sessions
Previous Message Fujii Masao 2020-02-18 04:16:56 Re: table partitioning and access privileges