Re: add PROCESS_MAIN to VACUUM
| От | Nathan Bossart |
|---|---|
| Тема | Re: add PROCESS_MAIN to VACUUM |
| Дата | |
| Msg-id | 20230301191344.GA1543729@nathanxps13 обсуждение исходный текст |
| Ответ на | Re: add PROCESS_MAIN to VACUUM (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
| Ответы |
Re: add PROCESS_MAIN to VACUUM
|
| Список | pgsql-hackers |
On Wed, Mar 01, 2023 at 07:09:53PM +0100, Alvaro Herrera wrote: > On 2023-Mar-01, Michael Paquier wrote: > >> +-- PROCESS_MAIN option >> +VACUUM (PROCESS_MAIN FALSE) vactst; >> +VACUUM (PROCESS_MAIN FALSE, PROCESS_TOAST FALSE) vactst; >> +VACUUM (PROCESS_MAIN FALSE, FULL) vactst; >> >> Thinking a bit here. This set of tests does not make sure that the >> main relation and/or the toast relation have been actually processed. >> pg_stat_user_tables does not track what's happening on the toast >> relations. So... What about adding some tests in 100_vacuumdb.pl >> that rely on vacuumdb --verbose and check the logs produced? We >> should make sure that the toast or the main relation are processed, >> by tracking, for example, logs like vacuuming "schema.table". When >> FULL is involved, we may want to track the changes on relfilenodes >> depending on what's wanted. > > Maybe instead of reading the log, read values from pg_stat_all_tables. Here is an attempt at that. Thanks for the idea. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
Вложения
В списке pgsql-hackers по дате отправления: