pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Ben Webber <ben.webber@egsgroup.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: pgsql-admin@postgresql.org, Alexander Stanier <alexander.stanier@egsgroup.com>
Subject: Re: Change in logging behaviour between 8.1 and 8.2
Date: Mon, 17 Nov 2008 15:18:56 +0000
Message-ID: <49218B60.70409@egsgroup.com> (raw)
In-Reply-To: <20081117145837.GG4291@alvh.no-ip.org>
References: <4901E4ED.7090301@egsgroup.com>
<6092.1224892561@sss.pgh.pa.us>
<49217587.4030709@egsgroup.com>
<20081117145837.GG4291@alvh.no-ip.org>
An interesting suggestion, but the problem with storing the logfiles in
a table for us would be that uncompressed, the log file for a day is
about 10 gigs. This would mean that an unacceptable amount of excess
data would accumulate in the database. It would be feasible however to
write a script to import the archived logfile into a new temporary
database on a different server, then use SQL to search it and delete the
db when finished.
Thanks for the suggestion though.
Ben.
Alvaro Herrera wrote:
> Ben Webber wrote:
>> Hi,
>>
>> I wrote a shell script to find the duration and the related statement in the log file and place them one after the other if the duration is over a specified time like this:-
>>
>> 2008-10-31 02:00:49 GMT [23683] [mp_live] LOG: statement: CLUSTER;
>> 2008-10-31 02:04:42 GMT [23683] [mp_live] LOG: duration: 232783.684 ms
>
> I wonder if you'd benefit from doing CSV logs and then storing them into
> a table. Querying using SQL is probably going to be easier (and more
> robust -- it'd work even with embedded newlines etc).
>
This message has been scanned for malware by SurfControl plc. www.surfcontrol.com
view thread (7+ messages) latest in thread
Message-ID: <49218B60.70409@egsgroup.com> Permalink: ../49218B60.70409@egsgroup.com/ Also on: postgresql.org/message-id/49218B60.70409@egsgroup.com ·
reply
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-admin@postgresql.org Cc: ben.webber@egsgroup.com, alvherre@commandprompt.com, alexander.stanier@egsgroup.com Subject: Re: Change in logging behaviour between 8.1 and 8.2 In-Reply-To: <49218B60.70409@egsgroup.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