Re: NDirectFileRead and Write

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: NDirectFileRead and Write
Date: 2008-09-16 09:12:03
Message-ID: 48CF7863.5080903@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> writes:
>> BTW, we have the word 'Direct' in ShowBufferUsage().
>> Can I keep it as-is?
>
>> ShowBufferUsage()
>> ! Shared blocks: ...
>> ! Local blocks: ...
>> ! Direct blocks: <R> read, <W> written
>
> Good point. Seems like it should be changed, but I am not sure to what.
> Ideas anyone?

How about "Temp blocks"? It might be slightly confusing that access to
temporary tables shows up in "Local blocks", rather than "Temp blocks",
though. But then again, temp_tablespaces already controls where the
files are created, among other things, so there's some precedence to
calling those things "temp".

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Russell Smith 2008-09-16 09:51:52 Re: no XLOG during COPY?
Previous Message Simon Riggs 2008-09-16 09:04:41 Re: rmgr hooks and contrib/rmgr_hook