X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E58153A4AB1 for ; Sat, 13 Nov 2004 17:13:50 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 19184-02 for ; Sat, 13 Nov 2004 17:13:44 +0000 (GMT) Received: from megazone.bigpanda.com (megazone.bigpanda.com [64.147.171.210]) by svr1.postgresql.org (Postfix) with ESMTP id B28E03A4AC6 for ; Sat, 13 Nov 2004 17:13:44 +0000 (GMT) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id BBD8E354BA; Sat, 13 Nov 2004 09:13:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id BA6A5354B8; Sat, 13 Nov 2004 09:13:42 -0800 (PST) Date: Sat, 13 Nov 2004 09:13:42 -0800 (PST) From: Stephan Szabo To: vivek singh Cc: pgsql-performance@postgresql.org Subject: Re: Insertion puzzles In-Reply-To: <20041113112609.18083.qmail@web10703.mail.yahoo.com> Message-ID: <20041113091029.L35307@megazone.bigpanda.com> References: <20041113112609.18083.qmail@web10703.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/201 X-Sequence-Number: 9155 On Sat, 13 Nov 2004, vivek singh wrote: > I am new to this group and postgresql. I am working on > a project which uses postgresql and project is time > critical. We did all optimization in our project but > postgresql seems to be a bottle-neck. To solve this we > run the database operations in a different thread. But > still, with large volume of data in database the > insert operation becomes very slow (ie. to insert 100 > records in 5 tables, it takes nearly 3minutes). That's pretty bad. What does the schema look like? Are there any foreign keys, triggers or rules being hit? > vacuum analyze helps a bit but performance improvement > is not much. > We are using the default postgres setting (ie. didn't > change postgresql.conf). Hmm, there are a few settings to try to change, although to be honest, I'm not sure which ones beyond shared_buffers (maybe try a couple thousand) are applicable to 7.1.3. You really should upgrade. Alot of serious bug fixes and performance enhancements have been made from 7.1.x to 7.4.x.