Howdy,
> If the temp table doesn't fit in memory, we will have to put it in
> backing store somewhere, and a disk is the logical place, right? I
> don't see a huge advantage of putting it in memory. We could prevent
> WAL writes for temp tables. That would help.
Yes, if it won't fit in memory then clearly it needs to be put out
to disk. I just thought if it could stay in memory then there is no
real reason to bother the disk at all.
I do realise that it's probably vastly easier said than done though,
the more you start treating temp tables as a special case the more
complex looking after them will get.
Just idle speculation on my part really, I just happen to be sitting
next to a server with a very noisy disk which remains idle most of
the time as selects are far more common in my app than insert/updates
The only exception to that is this temp table, which is been using
fairly frequently and makes the thing grind away.
--
Paul McGarry mailto:paulm@opentec.com.au
Systems Integrator http://www.opentec.com.au
Opentec Pty Ltd http://www.iebusiness.com.au
6 Lyon Park Road Phone: (02) 9870 4718
North Ryde NSW 2113 Fax: (02) 9878 1755
--------------------------------------------------------------------
This document and any attachments are intended solely for
the named addressee(s), are confidential, and may be subject to
legal professional privilege. Please notify us (on +61-2 9878 1744)
as soon as possible if you have received this document in error.
Any confidentiality or privilege is not waived or lost because this
email has been sent to you by mistake. This document and any
attachments are subject to copyright. No part of them should be
reproduced or distributed by any means whatsoever without the
prior consent of the copyright owner. Opentec does not warrant
that this email and any attachments are error or virus free.
--------------------------------------------------------------------