Re: log_newpage header comment - Mailing list pgsql-hackers

From Robert Haas
Subject Re: log_newpage header comment
Date
Msg-id CA+TgmobondAWvFbtouhwmMy4Y3P50=6JA6C_ek3x7V1bVt4PRg@mail.gmail.com
Whole thread Raw
In response to Re: log_newpage header comment  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: log_newpage header comment
Re: log_newpage header comment
List pgsql-hackers
On Fri, Jun 8, 2012 at 9:56 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> OK.  So what I'm thinking is that we should add a new function that
> takes a relfilenode and a buffer and steps 4-6 of what's described in
> transam/README: mark the buffer dirty, xlog it, and set the LSN and
> TLI.  We might want to have this function assert that it is in a
> critical section, for the avoidance of error.  Then anyone who wants
> to use it can do steps 1-3, call the function, and then finish up with
> steps 6-7.  I don't think we can cleanly encapsulate any more than
> that.

On further review, I think that we ought to make MarkBufferDirty() the
caller's job, because sometimes we may need to xlog only if
XLogIsNeeded(), but the buffer's got to get marked dirty either way.
So I think the new function should just do step 5 - emit XLOG and set
LSN/TLI.

Proposed patch attached.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Checkpointer on hot standby runs without looking checkpoint_segments
Next
From: Amit kapila
Date:
Subject: WIP patch for Todo Item : Provide fallback_application_name in contrib/pgbench, oid2name, and dblink