Re: New vacuum option to do only freezing - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: New vacuum option to do only freezing
Date
Msg-id CAH2-WznEhPi0k10hzeBi-0OSxzgpTi6k5jiqFnvOxHbA7gtjnA@mail.gmail.com
Whole thread Raw
In response to Re: New vacuum option to do only freezing  (Michael Paquier <michael@paquier.xyz>)
Responses Re: New vacuum option to do only freezing
List pgsql-hackers
On Tue, Jun 18, 2019 at 10:39 PM Michael Paquier <michael@paquier.xyz> wrote:
> +INSERT INTO no_index_cleanup(i, t) VALUES(1, repeat('1234567890',30000));
> Do we really need a string as long as that?

Specifying EXTERNAL storage might make things easier. I have used
PLAIN storage to test the 1/3 of a page restriction within nbtree, and
to test a bug in amcheck that was related to TOAST compression.

> It seems to me that we'd want tests to make sure that indexes are
> actually cleaned up, where pageinspect could prove to be useful.

That definitely seems preferable, but it'll be a bit tricky to do it
in a way that doesn't run into buildfarm issues due to alignment. I
suggest an index on a text column to avoid problems.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Update list of combining characters
Next
From: Peter Eisentraut
Date:
Subject: Re: pg_upgrade: Improve invalid option handling