From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_checkpointer is not a verb or verb phrase |
Date: | 2022-07-05 17:38:43 |
Message-ID: | CA+TgmoadmLU9jv0Kz7kKUAW7szkkMFHfuHqZ71dLdOoFwuEuag@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 1, 2022 at 5:50 PM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
> On Fri, Jul 01, 2022 at 03:36:48PM +0200, Magnus Hagander wrote:
> > +1 for pg_checkpoint on that -- let's not make it longer than necessary.
> >
> > And yes, +1 for actually changing it. It's a lot cheaper to change it now
> > than it will be in the future. Yes, it would've been even cheaper to have
> > already changed it, but we can't go back in time...
>
> Yeah, pg_checkpoint seems like the obvious alternative to pg_checkpointer.
> I didn't see a patch in this thread yet, so I've put one together. I did
> not include the catversion bump.
Hearing several votes in favor and none opposed, committed and
back-patched to v15. I added the catversion bump, but left out the .po
file changes, figuring it was better to let those files get updated
via the normal process.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jacob Champion | 2022-07-05 17:43:21 | Re: generic plans and "initial" pruning |
Previous Message | Melanie Plageman | 2022-07-05 17:24:55 | Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?) |