From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Track Oldest Initialized WAL Buffer Page |
Date: | 2023-03-01 04:19:31 |
Message-ID: | 20230301041931.GB1453450@nathanxps13 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 28, 2023 at 11:12:29AM +0530, Bharath Rupireddy wrote:
> On Tue, Feb 28, 2023 at 5:52 AM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>> It's confusing to me that OldestInitializedPage is set to NewPageBeginPtr.
>> Doesn't that set it to the beginning of the newest initialized page?
>
> Yes, that's the intention, see below. OldestInitializedPage points to
> the start address of the oldest initialized page whereas the
> InitializedUpTo points to the end address of the latest initialized
> page. With this, one can easily track all the WAL between
> OldestInitializedPage and InitializedUpTo.
This is where I'm confused. Why would we set the variable for the start
address of the _oldest_ initialized page to the start address of the
_newest_ initialized page? I must be missing something obvious, so sorry
if this is a silly question.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2023-03-01 04:29:19 | Re: Weird failure with latches in curculio on v15 |
Previous Message | Nathan Bossart | 2023-03-01 04:15:23 | Re: Improve WALRead() to suck data directly from WAL buffers when possible |