From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: logtape.c stats don't account for unused "prefetched" block numbers |
Date: | 2020-09-15 07:00:54 |
Message-ID: | CAH2-Wz=15hLpbKRWTff5W=e31j3BRN0z24QCad5EBo1jVk_y5w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Sep 14, 2020 at 11:52 PM Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> On Thu, 2020-09-10 at 18:42 -0700, Peter Geoghegan wrote:
> > We still need to put the reliance on ltsWriteBlock() allocating many
> > blocks before they've been logically written on some kind of formal
> > footing for Postgres 13 -- it is now possible that an all-zero block
> > will be left behind even after we're done writing and have flushed
> > all
> > temp buffers, which is a new thing.
>
> Is the current direction of this thread (i.e. the two posted patches)
> addressing your concern here?
Yes.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2020-09-15 07:22:25 | Re: Allow ERROR from heap_prepare_freeze_tuple to be downgraded to WARNING |
Previous Message | Jeff Davis | 2020-09-15 06:52:32 | Re: logtape.c stats don't account for unused "prefetched" block numbers |