Skip site navigation (1) Skip section navigation (2)

Re: idea: global temp tables

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>,"Greg Stark" <stark(at)enterprisedb(dot)com>,"Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>,"PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: idea: global temp tables
Date: 2009-04-29 18:04:24
Message-ID: 49F85057.EE98.0025.0@wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote: 
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> Any chance that some of these improvements could be applied to temp
>> tables created with the PostgreSQL-specific syntax while we're at
>> it? 
> 
> You mean the Postgres-specific behavior, no?
> 
> Trying to support a table without *any* pre-existing catalog entries
> seems even harder than doing it without changing the pre-existing
> catalog entries.
 
I can't say that I followed all of Greg's ideas, but it seemed that
some of them related to cheaper ways to materialize the body of the
temp table, as opposed to updating the system tables.  That seemed
like it might be orthogonal to the issue of persistent temp table
definitions, and perhaps the ideas could help performance of all temp
tables, including the PostgreSQL-specific variety.  Being out of my
depth on the technical issues he was discussing, I can't really do
more than pose the question, however....
 
-Kevin

In response to

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2009-04-29 18:30:43
Subject: Re: idea: global temp tables
Previous:From: Dimitri FontaineDate: 2009-04-29 18:03:14
Subject: Re: Restore deleted rows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group