Re: LogwrtResult contended spinlock - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: LogwrtResult contended spinlock
Date
Msg-id 51111525fb84ecdadaf99c13a2fa63e4be08041e.camel@j-davis.com
Whole thread Raw
In response to Re: LogwrtResult contended spinlock  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: LogwrtResult contended spinlock
List pgsql-hackers
On Sun, 2024-04-07 at 14:19 +0200, Alvaro Herrera wrote:
> I pushed the "copy" pointer now, except that I renamed it to
> "insert",
> which is what we call the operation being tracked.  I also added some
> comments.

The "copy" pointer, as I called it, is not the same as the "insert"
pointer (as returned by GetXLogInsertRecPtr()).

LSNs before the "insert" pointer are reserved for WAL inserters (and
may or may not have made it to WAL buffers yet). LSNs before the "copy"
pointer are written to WAL buffers with CopyXLogRecordToWAL() (and may
or may not have been evicted to the OS file yet).

Other than that, looks good, thank you.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Erik Wienhold
Date:
Subject: Re: ❓ JSON Path Dot Precedence
Next
From: Melanie Plageman
Date:
Subject: Re: Use streaming read API in ANALYZE