Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT.

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Jeff Davis <pgsql@j-davis.com>, Stephen Frost <sfrost@snowman.net>, "Bossart, Nathan" <bossartn@amazon.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-11-07T18:46:49Z
Lists: pgsql-hackers
On 2021-11-05 08:42:58 -0400, Robert Haas wrote:
> On Thu, Nov 4, 2021 at 7:38 PM Jeff Davis <pgsql@j-davis.com> wrote:
> > It seems like this specific approach has been mostly shot down already.
> >  But out of curiosity, are you intending to run CHECKPOINT during
> > bootstrap or something?
> 
> Imagine a system with corruption in pg_proc. Right now, that won't
> prevent you from successfully executing a checkpoint. With this
> approach, it might.

Exactly. It wouldn't matter if checkpoints weren't something needed to
potentially bring the system back into a sane state, but ...



Commits

  1. Add pg_checkpointer predefined role for CHECKPOINT command.