Mime-Version: 1.0 (Apple Message framework v622)
In-Reply-To: <1114025818.66326.34.camel@home>
References: <6f4567d4e64297b356e2d71ec392cdae@richardplotkin.com>
	<1114025818.66326.34.camel@home>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <73a30faf07358bdb7935f97f50dd1189@richardplotkin.com>
Content-Transfer-Encoding: 7bit
From: Richard Plotkin <richard@richardplotkin.com>
Subject: Re: Disk filling, CPU filling, renegade inserts and deletes?
Date: Wed, 20 Apr 2005 13:43:50 -0700
To: pgsql-performance@postgresql.org

As a follow-up, I've found a function that used the following code:

CREATE TEMPORARY TABLE results
(nOrder integer,
page_id integer,
name text)
WITHOUT OIDS
ON COMMIT DROP;

I would assume that the "WITHOUT OIDS" would be part of the source of 
the problem, so I've commented it out.

On Apr 20, 2005, at 12:36 PM, Rod Taylor wrote:

>> I'm having a pretty serious problem with postgresql's performance.
>> Currently, I have a cron task that is set to restart and vacuumdb -faz
>> every six hours.  If that doesn't happen, the disk goes from 10% full
>> to 95% full within 2 days (and it's a 90GB disk...with the database
>> being a 2MB download after dump), and the CPU goes from running at
>> around a 2% load to a 99+% load right away (the stats look like a
>> square wave).
>
> Are you running frequent queries which use temporary tables?
>
>
> -- 
>