| From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | "Gregory Stark" <stark(at)enterprisedb(dot)com> |
| Cc: | "Jaime Casanova" <systemguards(at)gmail(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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 10:01:08 |
| Message-ID: | 162867790707030301s42e7f5adq1f58f8320e9c4ad5@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > Global temp table can be created from template only when is used. It's
> > has not negative efect on app which doesn't use it. The benefit of
> > g.t.t. is simplifycation of stored procedures.
>
> And if it's used in 200 txns/s? Imagine the earlier poster who was looking for
> a way to display the count of records matching a search followed by the ten
> records on the page without re-executing the search.
>
I wrote about comparation global temp tables and current temp tables.
Counting of result's records is problem. I know. It's incompleteness
of current cursor's implementation. Every cursor can be materialised
and then can be counted. We need operation OPEN which matarialise
cursor and returns real row_count.
Regards
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-07-03 10:50:02 | Re: Proposal: In-Place upgrade concept |
| Previous Message | Gregory Stark | 2007-07-03 09:59:57 | Re: what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL |