| From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Jim Nasby" <decibel(at)decibel(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL |
| Date: | 2007-07-03 05:14:24 |
| Message-ID: | 162867790707022214k239217afj13400b284a85eb4e@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> > How about a new relkind which causes the table to be located in
> > PGDATA/base/<dboid>/pg_temp_<backendid>/<relfilenode>
> > So each backend can have its own copy of the table with the same
> > relfilenode; there's no need for extra catalog entries.
>
> Uh-huh. And what do you do with relpages, reltuples, relfrozenxid, and
> pg_statistic entries? What if one backend wants to TRUNCATE or CLUSTER
> its copy (requiring a new relfilenode)? Where does ALTER TABLE fit into
> this?
>
This entries can be teoreticly virtual (in memory). If we have some
memory storage we can use it for it.
nice a day
Pavel Stehule
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2007-07-03 07:53:28 | Re: [COMMITTERS] pgsql: Fix PGXS conventions so that extensions can be built against |
| Previous Message | Pavel Stehule | 2007-07-03 05:08:36 | Re: what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL |