| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT. |
| Date: | 2021-10-25 16:10:23 |
| Message-ID: | BA225AFF-7778-41C8-8B59-92B0C423BCF8@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/24/21, 11:13 PM, "Jeff Davis" <pgsql(at)j-davis(dot)com> wrote:
> On Sun, 2021-10-24 at 21:32 +0000, Bossart, Nathan wrote:
>> My initial reaction was that members of pg_maintenance should be able
>> to do all of these things (VACUUM, ANALYZE, CLUSTER, REINDEX, and
>> CHECKPOINT).
>
> What about REFRESH MATERIALIZED VIEW? That seems more specific to a
> workload, but it's hard to draw a clear line between that and CLUSTER.
Hm. CLUSTER reorders the content of a table but does not change it.
REFRESH MATERIALIZED VIEW, on the other hand, does replace the
content. I think that's the sort of line I'd draw between REFRESH
MATERIALIZED VIEW and the other commands as well, so I'd leave it out
of pg_maintenance.
Nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2021-10-25 16:12:27 | Re: XTS cipher mode for cluster file encryption |
| Previous Message | Tom Lane | 2021-10-25 15:59:52 | Re: [PATCH] Fix memory corruption in pg_shdepend.c |