Greg Smith wrote:
> Jonas J wrote:
> >P.S.: I'm using PostgreSQL 8.1.4 to run with TPCC-UVA benchmarks tests...
> Ah. PostgreSQL 8.1 is significantly slower than the current
> versions, and you're not going to get as much help with issues
> related to the source code as if you're using a newer on
Thanks for the answers.
I will change it for PostgreSQL 8.4 and try to use DBT-2.
But, I'm not quite sure if DTrace will give me the workload that I want.
Since, i want to trace the Workload that is above the Buffer Layer. With
workload I mean two fields (operation: read/write and Block Number). T
Jonas J wrote:
I took a look in the code again and made some changes. For the
readBuffer im doing now:
ReadBuffer(Relation reln, BlockNumber blockNum)
fprintf(fp,"r%u\n",(unsigned int) blockNum); //as defined in
header, typedef uint32 BlockNumber;
and from the write pages:
write_buffer(B
On Sun, Dec 6, 2009 at 9:04 AM, Greg Smith wrote:
> And that won't work at all. "Buffer" is a structure, not an integer. You
> need to wait until it's been locked, then save the same data as on the read
> side (relation and block number) from inside the structure. You probably
> want to hook Fl
Jonas J wrote:
Buffer
ReadBuffer(Relation reln, BlockNumber blockNum)...
fprintf(fp,"Read Block n: %d\n",(int) blockNum);
The "key" as it were for database blocks read is both of the things
passed into ReadBuffer. You'd need to save both the Relation number
(which turns into the subdirecto
Hi,
I'm a Computer Science student and I'm currently studying databases buffer
managers. I want to do some experiments and see how the pages access works
in PostgreSQL. (and I also will do some I/O experiments)
So, I want to do a "sniffer" on the Storage Layer of Postgresql. It should
work telli
