Re: Performance with temporary table

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: samantha mahindrakar <sam(dot)mahindrakar(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Performance with temporary table
Date: 2008-04-08 16:17:45
Message-ID: 20080408161745.GB9062@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

samantha mahindrakar escribió:

> So the program necessarily creates a temporary table evrytime it has
> to correct a record. However this table is dropeed after each record
> is corrected.

Perhaps it would be better to truncate the temp table instead.

> Iam not sure if i can use a cursor to replicate the functionality of
> the temp table. Is the performance bad because of the creation and
> deletion of the temp table?

Yes -- if you create/drop thousands of temp tables (or create/drop the
same temp table thousands of time), the resulting catalog bloat is
likely to hinder performance. Perhaps autovacuum should be at work here
(and if not you can solve the issue with manual vacuums to the system
catalogs), but even then it is at best unnecessary.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Oleg Bartunov 2008-04-08 17:38:56 Re: Re: what worked: performance improvements for geo-spatial searching on FreeBSD
Previous Message Richard Huxton 2008-04-08 15:50:43 Re: Performance with temporary table