Re: [PERFORM] Big IN() clauses etc : feature proposal
| От | Martijn van Oosterhout |
|---|---|
| Тема | Re: [PERFORM] Big IN() clauses etc : feature proposal |
| Дата | |
| Msg-id | 20060511184346.GL30113@svana.org обсуждение |
| Ответ на | Re: [PERFORM] Big IN() clauses etc : feature proposal (Greg Stark <gsstark@mit.edu>) |
| Ответы |
Re: [PERFORM] Big IN() clauses etc : feature proposal
|
| Список | pgsql-hackers |
On Thu, May 11, 2006 at 11:35:34AM -0400, Greg Stark wrote: > I can say that I've seen plenty of instances where the ability to create > temporary tables very quickly with no overhead over the original query would > be useful. I wonder if this requires what the standard refers to as a global temporary table. As I read it (which may be wrong, I find the language obtuse), a global temporary table is a temporary table whose structure is predefined. So, you'd define it once, updating the catalog only once but still get a table that is emptied each startup. Ofcourse, it may not be what the standard means, but it still seems like a useful idea, to cut down on schema bloat. Have a nice day, -- Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to litigate.
В списке pgsql-hackers по дате отправления: