Re: Incremental results from libpq
От | Goulet, Dick |
---|---|
Тема | Re: Incremental results from libpq |
Дата | |
Msg-id | 4001DEAF7DF9BD498B58B45051FBEA6502EF5628@25exch1.vicorpower.vicr.com обсуждение исходный текст |
Ответ на | Incremental results from libpq (Scott Lamb <slamb@slamb.org>) |
Ответы |
Re: Incremental results from libpq
|
Список | pgsql-interfaces |
Alvaro, You are quite correct, which is functionally the only difference. Personally I don't think that really amounts to "a hill of beans". The functionality is the same, even if the syntax is a touch different. Course, I didn't get a chance to tinker with this, but in Oracle a global temp table can have indexes and constraints. Is the same true in Postgresql?? I've found it to be a performance improver where your loading the temp table with thousands of rows. -----Original Message----- From: Alvaro Herrera [mailto:alvherre@commandprompt.com] Sent: Wednesday, November 16, 2005 7:51 PM To: Bruce Momjian Cc: Goulet, Dick; Tom Lane; Peter Eisentraut; pgsql-interfaces@postgresql.org; Scott Lamb Subject: Re: [INTERFACES] Incremental results from libpq Bruce Momjian wrote: > Goulet, Dick wrote: > > > If I may, one item that would be of extreme use to our location > > would be global temporary tables. These have existed since Oracle 9.0. > > They are defined once and then used by clients as needed. Each session > > is ignorant of the data of any other session and once you disconnect the > > data from the session disappears. Truly a real temporary table. > > How is it better than what we have now? Global temporary tables are defined only once (not once per session), and the schema (definition) is known to all sessions. Only the content is private to each session. At least that's what I remember since the last time I read the spec on it ... -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-interfaces по дате отправления: