Re: [HACKERS] NDirectFileRead and Write

2008-09-17 Thread Tom Lane
ITAGAKI Takahiro <[EMAIL PROTECTED]> writes: > - NDirectFile{Read|Write} are renamed to BufFile{Read|Write}Count. > - They are still declared in execdebug.h and buffile.c includes it. After some thought I concluded that the least ugly way to do this was to declare and define the variables in the s

Re: [HACKERS] NDirectFileRead and Write

2008-09-16 Thread Heikki Linnakangas
Tom Lane wrote: ITAGAKI Takahiro <[EMAIL PROTECTED]> writes: BTW, we have the word 'Direct' in ShowBufferUsage(). Can I keep it as-is? ShowBufferUsage() ! Shared blocks: ... ! Local blocks: ... ! Direct blocks: read, written Good point. Seems like it should be changed, but I am no

Re: [HACKERS] NDirectFileRead and Write

2008-09-15 Thread ITAGAKI Takahiro
Here is a revised patch to renewal NDirectFileRead/Write. > Tom Lane <[EMAIL PROTECTED]> wrote: > > * Let's rename them BufFileReadCount and BufFileWriteCount to reflect > > their actual purpose. > > * In any case I agree that the current arrangement > > with execdebug.h declaring variables define

Re: [HACKERS] NDirectFileRead and Write

2008-09-12 Thread Tom Lane
ITAGAKI Takahiro <[EMAIL PROTECTED]> writes: > BTW, we have the word 'Direct' in ShowBufferUsage(). > Can I keep it as-is? > ShowBufferUsage() > ! Shared blocks: ... > ! Local blocks: ... > ! Direct blocks: read, written Good point. Seems like it should be changed, but I am not sure to

Re: [HACKERS] NDirectFileRead and Write

2008-09-12 Thread ITAGAKI Takahiro
Tom Lane <[EMAIL PROTECTED]> wrote: > * Let's rename them BufFileReadCount and BufFileWriteCount to reflect > their actual purpose. It looks good. No one uses NDirectFileRead/Write variables now, so we can rename it freely. BTW, we have the word 'Direct' in ShowBufferUsage(). Can I keep it as-i

Re: [HACKERS] NDirectFileRead and Write

2008-09-11 Thread Tom Lane
ITAGAKI Takahiro <[EMAIL PROTECTED]> writes: > Here is a patch to user NDirectFileRead/Write counters to get I/O counts > in BufFile module. We can see the counters when log_statement_stats is on. Couple thoughts here: * Let's rename them BufFileReadCount and BufFileWriteCount to reflect their ac

Re: [HACKERS] NDirectFileRead and Write

2008-09-08 Thread ITAGAKI Takahiro
"Hitoshi Harada" <[EMAIL PROTECTED]> wrote: > so I guess all of these variables should be defined together but > actually you put the two in buffile.h while the others in > buf_internals.h. Is there clear reason for that? That's because buffile.c includes buffile.h, but not buf_internals.h . NDi

Re: [HACKERS] NDirectFileRead and Write

2008-09-06 Thread Hitoshi Harada
2008/8/5 ITAGAKI Takahiro <[EMAIL PROTECTED]>: > Here is a patch to user NDirectFileRead/Write counters to get I/O counts > in BufFile module. We can see the counters when log_statement_stats is on. > > The information is different from trace_sort; trace_sort shows used blocks > in external sort, a

Re: [HACKERS] NDirectFileRead and Write

2008-08-04 Thread ITAGAKI Takahiro
Here is a patch to user NDirectFileRead/Write counters to get I/O counts in BufFile module. We can see the counters when log_statement_stats is on. The information is different from trace_sort; trace_sort shows used blocks in external sort, and log_statement_stats shows how many I/Os are submitted

[HACKERS] NDirectFileRead and Write

2008-08-01 Thread ITAGAKI Takahiro
Hello, I'd like to use NDirectFileRead and NDirectFileWrite statistics counters for counting reads and writes in BufFile. They are defined, but not used now. BufFile is used for tuple sorting or materializing, so we could use NDirectFileRead/Write to retrieve how many I/Os are done in temp tablesp