Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 5D9C3632515 for ; Tue, 20 Jan 2009 17:09:56 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 13365-07 for ; Tue, 20 Jan 2009 17:09:53 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mail.postgresql.org (Postfix) with ESMTP id 28313632514 for ; Tue, 20 Jan 2009 17:09:53 -0400 (AST) Received: by yw-out-2324.google.com with SMTP id 3so1436281ywj.73 for ; Tue, 20 Jan 2009 13:09:52 -0800 (PST) Received: by 10.150.182.16 with SMTP id e16mr2325877ybf.144.1232485791952; Tue, 20 Jan 2009 13:09:51 -0800 (PST) Received: by 10.151.146.16 with HTTP; Tue, 20 Jan 2009 13:09:51 -0800 (PST) Message-ID: <3073cc9b0901201309p3d2d6715u550c7794c08dc0b8@mail.gmail.com> Date: Tue, 20 Jan 2009 16:09:51 -0500 From: "Jaime Casanova" To: "Bryce Nesbitt" Subject: Re: New pg_dump patch, --no-stats flag, disables sending to statistics collector Cc: "Pgsql Hackers" In-Reply-To: <49763C47.7070400@obviously.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <483FD205.4090904@sigaev.ru> <490B07BA.6030109@sigaev.ru> <492F04D9.5070404@enterprisedb.com> <4942A137.3000502@sigaev.ru> <1229910966.2285.76.camel@jdavis> <49708008.8070109@sigaev.ru> <1232348905.7281.114.camel@jdavis> <4974B002.3040202@sigaev.ru> <1232474489.23316.8.camel@jdavis> <49763C47.7070400@obviously.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200901/1476 X-Sequence-Number: 132120 On Tue, Jan 20, 2009 at 4:04 PM, Bryce Nesbitt wrote= : > This patch adds another flag to pg_dump, this time to disable statistics > collection. This is useful if your don't want pg_dump activity to show (= or > clutter) your normal statistics. This may be appropriate for an > organization that regularly dumps a database for backup purposes, but wan= ts > to analyze only the application's database use. > i haven't looked at the patch nor it's functional use... but from the top of my head jumps a question: is there a reason to not make this the default behaviour? --=20 Atentamente, Jaime Casanova Soporte y capacitaci=F3n de PostgreSQL Asesor=EDa y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157