postgres to hog the CPU for any extended period (other apps also run on the server), so I was wondering if the general config settings could to be tuned to always prevent this (regardless of how poorly written my queries are :)?
Neil
On 12/07/06, Jeff Frost <[EMAIL PROTECTED]> wrote:
O
Thanks for the tip; I'll try that when we initially upgrade, hopefully soon.
Neil
On 12/07/06, Bruno Wolff III <[EMAIL PROTECTED]> wrote:
On Mon, Jul 10, 2006 at 17:55:38 +1000,Neil Hepworth <[EMAIL PROTECTED]
> wrote:>> running on our server (obviously we need to updat
) (actual
time=206.01..206.01 rows=0 loops=1)
-> Seq Scan on fttemp1600384653 (cost=0.00..0.00 rows=1
width=4) (actual time=206.00..206.00 rows=0 loops=1)
Total runtime: 3767.52 msec
Thanks,
Neil
On 10/07/06, Neil Hepworth <[EMAIL PROTECTED]> wrote:
Thanks for the reply.
T
EMAIL PROTECTED]> wrote:
On Mon, 10 Jul 2006, Neil Hepworth wrote:
> I am running PostgreSQL 7.3 on a Linux box (RHEL 2.1 - Xeon 2.8GHz
> with 1GB of RAM) and seeing very high CPU usage (normally over 90%)
> when I am running the following queries, and the queries take a long
> time to
Hi,
I am running PostgreSQL 7.3 on a Linux box (RHEL 2.1 - Xeon 2.8GHz
with 1GB of RAM) and seeing very high CPU usage (normally over 90%)
when I am running the following queries, and the queries take a long
time to return; over an hour!
CREATE TEMPORARY TABLE fttemp1600384653 AS SELECT * FROM f
