Re: Add mode column to pg_stat_progress_vacuum - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: Add mode column to pg_stat_progress_vacuum
Date
Msg-id CAA5RZ0suoicwxFeK_eDkUrzF7s0BVTaE7M+ehCpYcCk5wiECpw@mail.gmail.com
Whole thread Raw
In response to Re: Add mode column to pg_stat_progress_vacuum  (Maciek Sakrejda <m.sakrejda@gmail.com>)
Responses Re: Add mode column to pg_stat_progress_vacuum
List pgsql-hackers
Hi,

The patch looks overall good to me. I have a few comments:

1/ I believe It is possible for the mode to flip to "failsafe" during the
operation since lazy_check_wraparound_failsafe() is checked in-flight.
I think this should be mentioned in the "mode" section of the documentation
in the "failsafe" description.

2/ It feels odd that we do not have parity of the "mode" column in
pg_stat_progress_analyze. Should we add a "mode" column
there also that shows if the analyze was triggered_by "manual" or
"autovacuum"? An autovacuum in a relation can trigger both
a vacuum and an analyze, and a VACUUM(ANALYZE) will
also do both.

--
Sami Imseih
Amazon Web Services (AWS)



pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: ON CONFLICT DO SELECT (take 3)
Next
From: Japin Li
Date:
Subject: Re: [PATCH] Add pg_get_database_ddl() function to reconstruct CREATE DATABASE statement