From: smiley2211 <smiley2211@yahoo.com>
To: pgsql-performance@postgresql.org
Subject: Re: How to ENABLE SQL capturing???
Date: Fri, 10 Aug 2007 14:43:13 -0700 (PDT)
Message-ID: <12099590.post@talk.nabble.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708101309230.1940@discord.home.frostconsultingllc.com>
References: <12060736.post@talk.nabble.com>
<20070808203612.GA26143@uio.no>
<bd8531800708081357i4f14b41axb0f19e444dc47a6e@mail.gmail.com>
<12096180.post@talk.nabble.com>
<Pine.LNX.4.64.0708101309230.1940@discord.home.frostconsultingllc.com>
Jeff,
You are CORRECT...my queries were going to /var/log/messages...had to get
the Linux Admin to grant me READ access to the file...
Thanks for your reply.
Michelle.
Jeff Frost wrote:
>
> Michelle,
>
> What platform are you on? If you're on linux, than logging to syslog will
> likely show up in the /var/log/messages file.
>
> On Fri, 10 Aug 2007, smiley2211 wrote:
>
>>
>> Hello all,
>>
>> I have ENABLED this 'log_min_duration_statement = 100" but I can't figure
>> out WHERE it's writing the commands to ...I have it set to 'syslogs' but
>> this file is 0 bytes :confused:
>>
>> Should I set other parameters in my postgresql.conf file???
>>
>> Thanks...Michelle
>>
>>
>> Bryan Murphy-3 wrote:
>>>
>>> we currently have logging enabled for all queries over 100ms, and keep
>>> the last 24 hours of logs before we rotate them. I've found this tool
>>> very helpful in diagnosing new performance problems that crop up:
>>>
>>> http://pgfouine.projects.postgresql.org/
>>>
>>> Bryan
>>>
>>> On 8/8/07, Steinar H. Gunderson <sgunderson@bigfoot.com> wrote:
>>>> On Wed, Aug 08, 2007 at 01:02:24PM -0700, smiley2211 wrote:
>>>>> I am trying to enable capturing of the submitted code via an
>>>>> application...how do I do this in Postgres? Performance is SLOW on my
>>>>> server and I have autovacuum enabled as well as rebuilt
>>>> indexes...whatelse
>>>>> should be looked at?
>>>>
>>>> Try "log_min_duration_statement = 100" in postgresql.conf; it will show
>>>> all
>>>> statements that take more than 100ms. Set to 0 to log _all_ statements,
>>>> or
>>>> -1 to turn the logging back off.
>>>>
>>>> /* Steinar */
>>>> --
>>>> Homepage: http://www.sesse.net/
>>>>
>>>> ---------------------------(end of
>>>> broadcast)---------------------------
>>>> TIP 6: explain analyze is your friend
>>>>
>>>
>>> ---------------------------(end of broadcast)---------------------------
>>> TIP 3: Have you checked our extensive FAQ?
>>>
>>> http://www.postgresql.org/docs/faq
>>>
>>>
>>
>>
>
> --
> Jeff Frost, Owner <jeff@frostconsultingllc.com>
> Frost Consulting, LLC http://www.frostconsultingllc.com/
> Phone: 650-780-7908 FAX: 650-649-1954
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
>
--
View this message in context: http://www.nabble.com/How-to-ENABLE-SQL-capturing----tf4238694.html#a12099590
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: smiley2211@yahoo.com
Subject: Re: How to ENABLE SQL capturing???
In-Reply-To: <12099590.post@talk.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox