From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Phil Endecott <spam_from_postgresql_general(at)chezphil(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Temporary tables and disk activity |
Date: | 2004-12-13 02:35:33 |
Message-ID: | 14584.1102905333@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Phil Endecott <spam_from_postgresql_general(at)chezphil(dot)org> writes:
> Tom Lane wrote:
>> In principle, therefore, the kernel could hold temp table data in its
>> own disk buffers and never write it out to disk until the file is
>> deleted. In practice, of course, the kernel doesn't know the data is
>> transient and will probably push it out whenever it has nothing else to
>> do.
> That makes sense. I suspect that I am seeing writes every 5 seconds,
> which looks like bdflush / update.
> But my connections normally only last for a second at most. In this
> case, surely the table would normally have been deleted before the
> kernel decided to write anything.
That does seem a bit odd, then. Can you strace a typical backend
session and see if it's doing anything to force a disk write?
(I'm too lazy to go check right now whether 7.4 handled temp tables
exactly the same as CVS tip does. I think it's the same but I might
be wrong.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2004-12-13 02:48:27 | Re: Query is not using index when it should |
Previous Message | Phil Endecott | 2004-12-13 00:46:24 | Re: Temporary tables and disk activity |