"Pavel Stehule" <[EMAIL PROTECTED]> writes: > if I understand well, there isn't any difference between local and > global temp tables in postgresql.
See the archives; some time ago we determined that the correct reading of the spec is that global/local determines visibility of temp tables across modules, but still within a single session. Since we don't have modules there is no difference for us. > I have question. Is correct implementation of global temp in Oracle or > Firebird, where content of glob.temp table is session visible and > metadata of g.t.t is persistent? It's correct per spec. Whether it's more useful than what we do is highly debatable --- it forces all sessions to use the same definition of any given temp table name, which is a bit silly for something that's supposed to support session-local data. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match