If you store the temp tables in RAM, how will you preserve the ACID property on power failure (without using write-through which would negate the speed advantage)?
The temp tables may be participating in a transaction. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Luiz Gonzaga da Mata Sent: Tuesday, January 25, 2005 2:18 PM To: pgsql-hackers@postgresql.org Subject: [HACKERS] Performance of the temporary table creation and use. Hi, A suggestion: I made a test creating one database specific through pgAdminIII.. I created database test. I created the table tb1 into test. CREATE temporary TABLE tb1 ( campo1 int2 NOT NULL ) WITH OIDS; Insert into tb1 values(1); The PostgreSQL creates a temporary schema pg_temp_(1-n). it physically places the table in this temporary schema and with a OID inside of the structure base/OID_do_database. Although to have changed they sort_mem/work_mem it for 1 MB, it did not use this area in available memory for the connection to make the creation of the temporary table. It has enough memory so that it was used. It would not be the case of beyond create index, create temporary table also to use this available resource? The performance would be another one in environments with much competition., not? This value of sort_mem/work_mem is configured and not used. Regards, Luiz Gonzaga da Mata ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
