Horton

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

Jeff Davis <pgsql@j-davis.com>

View thread View on postgr.es
From: Jeff Davis <pgsql@j-davis.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: "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-10-26T21:03:24Z
Lists: pgsql-hackers 
On Tue, 2021-10-26 at 16:02 -0400, Stephen Frost wrote:
> We're talking about benchmarking tools

What I had in mind was something much less formal, like a self-
contained repro case of a performance problem.

  ... simple schema
  ... data load
  ... maybe build some indexes
  ... maybe set hints
  VACUUM ANALYZE;
  CHECKPOINT;

I'm not saying it's a very strong use case, but at least for me, it's
kind of a habit to throw in a CHECKPOINT after a quick data load for a
test, even if it might not matter for whatever I'm testing.

I guess I can change my habit to use a function instead, but then
what's the point of the syntax?

Should we just add a builtin function pg_checkpoint(), and deprecate
the syntax?

Regards,
	Jeff Davis

Commits

  1. Add pg_checkpointer predefined role for CHECKPOINT command.