X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5D71FDAB8F for ; Tue, 25 Oct 2005 13:05:00 -0300 (ADT) 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 45593-08 for ; Tue, 25 Oct 2005 16:04:48 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 79B68D87C9 for ; Tue, 25 Oct 2005 13:04:48 -0300 (ADT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id j9PG49sH003152 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 25 Oct 2005 10:04:11 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.4/8.13.4) with ESMTP id j9PG497J053693; Tue, 25 Oct 2005 10:04:09 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.4/8.13.4/Submit) id j9PG489a053692; Tue, 25 Oct 2005 10:04:09 -0600 (MDT) (envelope-from mfuhr) Date: Tue, 25 Oct 2005 10:04:08 -0600 From: Michael Fuhr To: jnevans@gmail.com Cc: pgsql-performance@postgresql.org Subject: Re: impact of stats_command_string Message-ID: <20051025160408.GA53661@winnie.fuhr.org> References: <1129840387.509093.90500@g49g2000cwa.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1129840387.509093.90500@g49g2000cwa.googlegroups.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200510/367 X-Sequence-Number: 15135 On Thu, Oct 20, 2005 at 01:33:07PM -0700, jnevans@gmail.com wrote: > If I turn on stats_command_string, how much impact would it have on > PostgreSQL server's performance during a period of massive data > INSERTs? Do you really need to be doing "massive data INSERTs"? Can you use COPY, which is much more efficient for bulk loads? http://www.postgresql.org/docs/8.0/interactive/populate.html -- Michael Fuhr