From: | Keith <keith(at)keithf4(dot)com> |
---|---|
To: | Ankur Kaushik <ankurkaushik(at)gmail(dot)com> |
Cc: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: seperate Slow log file |
Date: | 2016-01-23 07:54:18 |
Message-ID: | CAHw75vv3BLNZrH2g1cKcAJ57j5kwv7AS57ZfxN6dLuZ64sRYEA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I highly recommend pgbadger
http://dalibo.github.io/pgbadger/
It will give you more analysis into your logs than a simple, separate slow
query log ever could.
On Sat, Jan 23, 2016 at 2:29 AM, Ankur Kaushik <ankurkaushik(at)gmail(dot)com>
wrote:
>
> So is there way to find the last error , Identify and discriminate slow
> queries on the bases of time taken . as while i use Mysql There are
> separate logs for slow,general and error logs. ?
>
> On Sat, Jan 23, 2016 at 12:14 PM, Guillaume Lelarge <
> guillaume(at)lelarge(dot)info> wrote:
>
>> Le 23 janv. 2016 6:59 AM, "Ankur Kaushik" <ankurkaushik(at)gmail(dot)com> a
>> écrit :
>> >
>> >
>> > To open the slow query log file I Change the variable as below
>> >
>> > log_min_duration_statement=100 in config file
>> >
>> > All Slow queries are logging in "postgresql-Sat.log" where errors also
>> comes to , So is there way to have separate slow query logs
>> >
>>
>> No, all logs go to the same log file.
>>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Thorsten Schöning | 2016-01-23 15:47:56 | Questions regarding handling of Postgres' stats data in case of tmpfs |
Previous Message | Ankur Kaushik | 2016-01-23 07:29:54 | Re: seperate Slow log file |