Dear Greg Stark,
Totally, right. I want to record the all updated region.
So, doing some work is not doing a little work.
But, I am trying to not touch the existing codes as much as I can.
Therefore, I mostly added my code, I didn't changed markDirtyBuffer function at
all, but, of course, I have
onday, October 26, 2009 5:32 AM
To: 노홍찬
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] a question about relkind of RelationData handed over to
heap_update function
On Mon, 26 Oct 2009, ??? wrote:
> What I am trying to do now is to examine the real dirty portion of
> buffer
On Mon, 26 Oct 2009, ??? wrote:
What I am trying to do now is to examine the real dirty portion of
buffer pages to be flushed like the following.
You can trivially use pg_buffercache for view this, and its code in
contrib/pg_buffercache will show you how to navigate the buffer cache data
too
Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Monday, October 26, 2009 12:07 AM
To: 노홍찬
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] a question about relkind of RelationData handed over to
heap_update function
=?ks_c_5601-1987?B?s+vIq8L5?= writes:
> I found
=?ks_c_5601-1987?B?s+vIq8L5?= writes:
> I found that the relkind fields of all RelationData which is handed over to
> heap_update are all the same as ¡®r¡¯.
Well, yeah: heap_update is applied to heaps (ordinary tables). Not indexes.
The indexes are generally updated in a separate operation after
Dear hackers,
I’m modifying backend source codes of pgsql.
While inspecting the heap_update function (src/backend/access/heapam.c),
I found that the relkind fields of all RelationData which is handed over to
heap_update are all the same as ‘r’.
I want to distinguish normal relatio
