| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: New strategies for freezing, advancing relfrozenxid early |
| Date: | 2023-01-02 19:45:11 |
| Message-ID: | CAH2-WzmQjX1FiwZfBy-LrNZ5KJc2tMjvk=oW2sYoDBLYuq=ANQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 31, 2022 at 12:45 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> On Sat, Dec 31, 2022 at 11:46 AM Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> > "We have no freeze plans to execute, so there's no cost to following
> > the freeze path. This is important in the case where the page is
> > entirely frozen already, so that the page will be marked as such in the
> > VM."
>
> I'm happy to use your wording instead -- I'll come up with a patch for that.
What do you think of the wording adjustments in the attached patch?
It's based on your suggested wording.
--
Peter Geoghegan
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Tweak-page-level-freezing-comments.patch | application/octet-stream | 4.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Fittl | 2023-01-02 19:50:04 | Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? |
| Previous Message | Tom Lane | 2023-01-02 19:44:52 | Re: Why is char an internal-use category |