Re: Idea for better handling of cntxDirty - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject Re: Idea for better handling of cntxDirty
Date
Msg-id 3705826352029646A3E91C53F7189E325186CF@sectorbase2.sectorbase.com
Whole thread Raw
In response to Idea for better handling of cntxDirty  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Wouldn't it work for cntxDirty to be set not by LockBuffer, but by
> XLogInsert for each buffer that is included in its argument list?

I thought to add separate call to mark context dirty but above
should work if all callers to XLogInsert always pass all
modified buffers - please check.

Vadim


pgsql-hackers by date:

Previous
From: "a person"
Date:
Subject: Locking Question
Next
From: Paul Ogden
Date:
Subject: Re: [SQL] Inconsistent or incomplete behavior obverse in where