From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Greg Stark" <gsstark(at)mit(dot)edu> |
Cc: | "Craig James" <craig_james(at)emolecules(dot)com>, <fabio(dot)lafarcioli(at)molinoalimonti(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Number of tables |
Date: | 2009-08-24 14:29:58 |
Message-ID: | 4A925D960200002500029FD3@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Greg Stark <gsstark(at)mit(dot)edu> wrote:
> Creating new catalog entries for [temp tables] gives up -- what I
> think is the whole point of their design -- their lack of DDL
> overhead.
As long as we're brainstorming... Would it make any sense for temp
tables to be created as in-memory tuplestores up to the point that we
hit the temp_buffers threshold? Creating and deleting a whole set of
disk files per temp table is part of what makes them so heavy.
(There's still the issue of dealing with the catalogs, of course....)
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-08-24 14:37:04 | Re: postgresql uses Hash-join, i need Nested-loop |
Previous Message | Fred Janon | 2009-08-24 09:24:59 | How to create a multi-column index with 2 dates using 'gist'? |