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

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, "Bossart, Nathan" <bossartn(at)amazon(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT.
Date: 2021-11-04 23:38:36
Message-ID: ae70a6ff7700a821849be0da6cd0da69e0e4b05e.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2021-11-04 at 15:42 -0700, Andres Freund wrote:
> I don't like this. This turns the checkpoint command which previously
> didn't
> rely on the catalog in the happy path etc into something that
> requires most of
> the backend to be happily up to work.

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?

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2021-11-04 23:47:42 Re: WIP: expression evaluation improvements
Previous Message Jeff Davis 2021-11-04 23:35:02 Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT.