getting data from multiple sources leads to the creation of a temporary table. Those tables are costly to create and should be avoided if possible or at least created only once and not inside every transaction. Here is a thread about cost of temporary tables on postgresql : http://www.nabble.com/Create-and-drop-temp-table-in-8.3.4-td20347767.html Which is summarized by this sentence : As I learned today, creating a temporary table in PostgreSQL can easily create four files and do dozens of updates to system tables; that's all before you start actually inserting any data into the temporary table. We could use ON COMMIT DELETE ROWS if the table are created only once per session. | |
| priority | normal |
|---|---|
| type | enhancement |
| appeared in | <not specified> |
| done in | <not specified> |
| load | 1.000 |
| load left | 1.000 |
| closed by | <not specified> |


#481437 FlotPlotView : crash if '&' appears in a label
Comments
would "Support unlogged tables using the UNLOGGED option in CREATE TABLE" (http://www.postgresql.org/docs/9.1/static/release-9-1.html) in Postgresql9.1 be helpful ?
I suspect we are moving from temporary tables with datafeed so this ticket might soon be deprecated.