Re: Idea for better handling of cntxDirty

From: "Mikheev, Vadim" <VMIKHEEV(at)sectordata(dot)com>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Idea for better handling of cntxDirty
Date: 2002-11-12 18:11:01
Message-ID: 3705826352029646A3E91C53F7189E325186CF@sectorbase2.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-11-12 18:12:48 Re: RC1?
Previous Message Paul Ogden 2002-11-12 17:39:13 Inconsistent or incomplete behavior obverse in where clause