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\\_%';
Best regards,
--
Lets call it Postgres
EnterpriseDB http://www.enterprisedb.com
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com
Twitter: singh_gurjeet
Skype: singh_gurjeet
Mail sent from my BlackLaptop device
select name, setting, source from pg_settings where name like E'log\\_%';
Best regards,
On Wed, Sep 23, 2009 at 3:13 AM, Chris Barnes <compuguruchrisbarnes@xxxxxxxxxxx> wrote:
Hello,
I looked for log_statement and it appears to be off? Strange.
#log_statement = 'none'#log_statement_stats = off
> To: compuguruchrisbarnes@xxxxxxxxxxx
> CC: pgsql-general@xxxxxxxxxxxxxx
> Subject: Re: Logging statements longer than 1000ms doesn't appear to work
> Date: Tue, 22 Sep 2009 15:08:39 -0400
> From: tgl@xxxxxxxxxxxxx
>> Chris Barnes <compuguruchrisbarnes@xxxxxxxxxxx> 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 to be logged?
>
> regards, tom lane
We are your photos. Share us now with Windows Live Photos.
--
Lets call it Postgres
EnterpriseDB http://www.enterprisedb.com
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com
Twitter: singh_gurjeet
Skype: singh_gurjeet
Mail sent from my BlackLaptop device