Re: New pg_dump patch, --no-stats flag, disables sending to statistics collector

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Bryce Nesbitt <bryce2(at)obviously(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: New pg_dump patch, --no-stats flag, disables sending to statistics collector
Date: 2009-01-20 22:40:34
Message-ID: 497652E2.4030902@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce,

> If this is a generally desired feature (and I question that), I think we
> need a more general solution.

I'd argue that it is generally desired (or some convenient workaround)
but not urgently so. I'd also argue that if we're going to have a
--no-stats flag, it should exist for the other client ultilites as well;
if I don't want pg_dump showing up, I probably don't want Vacuum showing
up, or various other already-debugged maintenance routines.

I'd suggest putting this into the first patch review for 8.5.

--Josh

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Treat 2009-01-20 23:08:20 Re: Status Report on Hot Standby
Previous Message James Mansion 2009-01-20 22:40:09 Re: libpq WSACleanup is not needed

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2009-01-20 23:37:11 Re: New pg_dump patch, --no-stats flag, disables sending to statistics collector
Previous Message Bryce Nesbitt 2009-01-20 22:15:44 Re: New pg_dump patch, --no-stats flag, disables sending to statistics collector