| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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-05 12:42:58 |
| Message-ID: | CA+Tgmob9TxDV3X4+=eG9E+o80MW_qoJjTvvHhRt252OO=X9FbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 4, 2021 at 7:38 PM Jeff Davis <pgsql(at)j-davis(dot)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.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-11-05 12:54:37 | Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT. |
| Previous Message | Robert Haas | 2021-11-05 12:40:27 | Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT. |