On Tue, Sep 22, 2009 at 3:55 PM, Gurjeet Singh wrote:
> Sometimes, your current postgresql.conf might not be in sync with server
> settings, for various reasons. I'd suggest looking at the output of:
>
> select name, setting, source from pg_settings where name like E'log\\_%';
Or
psql dbname
sho
compuguruchrisbar...@hotmail.com> wrote:
> Hello,
>
> I looked for log_statement and it appears to be off? Strange.
>
> #log_statement = 'none'
> #log_statement_stats = off
>
> > To: compuguruchrisbar...@hotmail.com
> > CC: pgsql-general@postgres
Hello,
I looked for log_statement and it appears to be off? Strange.
#log_statement = 'none'
#log_statement_stats = off
> To: compuguruchrisbar...@hotmail.com
> CC: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Logging statements longer than 1000ms doesn&
I checked and this is the only refererences. Were usng 8.3.3.
#log_statement = 'none' # none, ddl, mod, all
#log_statement_stats = off
> To: compuguruchrisbar...@hotmail.com
> CC: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Logging statements
Chris Barnes writes:
> I've have set the parameter in my postgresql.conf file and have restarted
> postgres.
> When reviewing the log file I am finding that all of the statements are being
> logged (0.108 ms)?
Perhaps you also set log_statement = all, or some other reason that
would cause them
I've have set the parameter in my postgresql.conf file and have restarted
postgres.
When reviewing the log file I am finding that all of the statements are being
logged (0.108 ms)?
Is there some other parameter that I have missed?
log_min_duration_statement = 1000 # -1 is disab
