Received: from mail.concept-factory.com (mail.concept-factory.com [204.181.16.156]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0SMAHl68804 for ; Mon, 28 Jan 2002 17:10:17 -0500 (EST) (envelope-from mitch@doot.org) Received: from Mitch (cx2156713-a.phnx1.az.home.com [24.38.178.119]) by mail.concept-factory.com (Postfix) with SMTP id B931741FC7 for ; Mon, 28 Jan 2002 15:10:15 -0700 (MST) Message-ID: <017901c1a848$eec1bb30$0200000a@Mitch> From: "Mitch Vincent" To: "PostGreSQL PHP Group" References: Subject: Re: pg_pconnect - ?? Date: Mon, 28 Jan 2002 15:12:52 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Archive-Number: 200201/83 X-Sequence-Number: 886 > The most traffic the user creates is when they change their rate > table, they might add 20 to 50 rates at per week. I could run that > stuff of an old 100 MHz Pentium with 16 MB RAM, if I had to and they > would probably not see and performance issues. However, some of the > bills they have process 500'000 line items at a time, this is where I > need the horsepower - but at that stage, the connection is already > made. The query runs across 4 tables and sometimes takes up to 4 > minutes. If you post schema and queries then perhaps we could help you get that time down a bit? Pardon the questions but you're indexing, VACUUM ANALYZE ' ing and using EXPLAIN to see what your query plans are -- right? I guess if we're going to open this can of worms we'd better take the conversation to pg-general though... Good luck! -Mitch