Re: disabling log_min_duration_statement from pg_dump?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: disabling log_min_duration_statement from pg_dump?
Date: 2010-03-08 22:57:20
Message-ID: 201003082257.o28MvKG02862@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jaime Casanova wrote:
> On Mon, Mar 8, 2010 at 4:25 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> writes:
> >> can we add a parameter in pg_dump and pg_dumpall to disable
> >> log_min_duration_statement?
> >
> > export PGOPTIONS="-c log_min_duration_statement=-1"
> >
>
> ah! so, that is PGOPTIONS for :)
> and that works for every libpq application?

Yes.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-03-08 23:03:11 Re: Re: incorrect exit code from psql with single transaction + violation of deferred FK constraint
Previous Message Hannu Krosing 2010-03-08 22:06:21 Re: invalid UTF-8 via pl/perl