Re: How to force "re-TOAST" after changing STORAGE or COMPRESSION?

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: rob stone <floriparob(at)tpg(dot)com(dot)au>, Michael Paquier <michael(at)paquier(dot)xyz>, Dominique Devienne <ddevienne(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: How to force "re-TOAST" after changing STORAGE or COMPRESSION?
Date: 2023-10-03 04:31:27
Message-ID: f8ddee9d35553f802b5c1b1968f6c4c72a1640f1.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 2023-10-03 at 12:33 +1100, rob stone wrote:
> Would running CLUSTER on the table use the new parameters for the re-
> write?

No, as far as I know.

You'd need something like

-- rewrite all tuples
UPDATE tab SET id = id;
-- get rid of the bloat
VACUUM (FULL) tab;

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2023-10-03 04:45:22 Re: How to force "re-TOAST" after changing STORAGE or COMPRESSION?
Previous Message rob stone 2023-10-03 01:33:54 Re: How to force "re-TOAST" after changing STORAGE or COMPRESSION?