On Thu, Mar 9, 2017 at 9:34 PM, Amit Kapila <amit.kapil...@gmail.com> wrote: > Do we really need to set LSN on this page (or mark it dirty), if so > why? Are you worried about restoration of FPI or something else?
I haven't thought through all of the possible consequences and am a bit to tired to do so just now, but doesn't it seem rather risky to invent a whole new way of using these xlog functions? src/backend/access/transam/README describes how to do write-ahead logging properly, and neither MarkBufferDirty() nor PageSetLSN() is described as an optional step. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
