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

2023-10-03 Thread Dominique Devienne
On Tue, Oct 3, 2023 at 9:17 AM Laurenz Albe wrote: > On Tue, 2023-10-03 at 09:08 +0200, Dominique Devienne wrote: > > In my case, it's OK not to be transactional, for these experiments. Is > there a way > > to lock the table and do the rewriting w/o generating any WAL? I don't > have any experie

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

2023-10-03 Thread Laurenz Albe
On Tue, 2023-10-03 at 09:08 +0200, Dominique Devienne wrote: >  In my case, it's OK not to be transactional, for these experiments. Is there > a way > to lock the table and do the rewriting w/o generating any WAL? I don't have > any experience > with unlogged tables, but should I take an exclusiv

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

2023-10-03 Thread Michael Paquier
On Tue, Oct 03, 2023 at 09:08:49AM +0200, Dominique Devienne wrote: > In my case, it's OK not to be transactional, for these experiments. Is > there a way > to lock the table and do the rewriting w/o generating any WAL? I don't have > any experience > with unlogged tables, but should I take an exc

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

2023-10-03 Thread Dominique Devienne
On Tue, Oct 3, 2023 at 6:45 AM Michael Paquier wrote: > On Tue, Oct 03, 2023 at 06:31:27AM +0200, Laurenz Albe wrote: > > 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. > > No

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

2023-10-02 Thread Michael Paquier
On Tue, Oct 03, 2023 at 06:31:27AM +0200, Laurenz Albe wrote: > 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. Note that under the hoods VACUUM FULL and CLUSTER use the same code path

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

2023-10-02 Thread Laurenz Albe
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 Al

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

2023-10-02 Thread rob stone
Hello, On Tue, 2023-10-03 at 08:57 +0900, Michael Paquier wrote: > On Mon, Oct 02, 2023 at 04:42:15PM +0200, Dominique Devienne wrote: > > According to the doc, the table is NOT changed. > > In my case, I DO want to have the bytea column rewritten > > according to the new STORAGE and/or COMPRESSIO

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

2023-10-02 Thread Michael Paquier
On Mon, Oct 02, 2023 at 04:42:15PM +0200, Dominique Devienne wrote: > According to the doc, the table is NOT changed. > In my case, I DO want to have the bytea column rewritten > according to the new STORAGE and/or COMPRESSION. > The doc doesn't mention how to achieve that. Yes, the compression ty

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

2023-10-02 Thread Dominique Devienne
Hi. If I do either or both of the changes below: ddevienne=> alter table dd alter column val set compression lz4; ALTER TABLE ddevienne=> alter table dd alter column val set storage extended; ALTER TABLE According to the doc, the table is NOT changed. In my case, I DO want to have the bytea colum