> Although it's unrelated to your query about an exception being raised, > a word of advice on temporary tables. (This may not be relevant to > your situation, but it's no small source of pain in one of the systems > I'm responsible for.) Significant use of temporary tables will cause > commensurately significant bloat in your system catalogs. We have a > system which, in the course of its "normal" operations, creates > hundreds of temporary tables for processing, aggregation, analysis, > and reporting. Thank you very much for sharing your real-time experience. Do you think that this "significantly bloated system catalogs" is caused because of the old version 8.2.3 we're running? Will this be resolved in latest PostgreSQL v9.0? BTW, what version of PostgreSQL are you handling? Doc says: " Temporary tables are automatically dropped at the end of a session, or optionally at the end of the current transaction (see ON COMMIT below). Any indexes created on a temporary table are automatically temporary as well." If temporary tables and its indexes are automatically dropped at the end of the session, why would it cause bloat in system catalogs? I hope you can make me understand by sharing your real-time experience. Again, thanks for your advice. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
