From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | pg(at)kuhnsteffen(dot)de |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Serverlog |
Date: | 2010-09-01 10:09:30 |
Message-ID: | AANLkTik6G-hoBK85XiXR8k_9qj=SHftPK27Kf6MrbY5G@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Wed, Sep 1, 2010 at 6:50 AM, Steffen Kuhn <pg(at)kuhnsteffen(dot)de> wrote:
> Hi Dave,
>
> I can remember that there was a discussion about optimze Log in Server-Status.
> Yesterday I saw some wired parse results.
> Sample:
>
> begin transaction;
> -- doing something ending with a newline
> -- doing something else ending with a newline
> -- doing something further ending with a newline
> insert something with a TIMESTAMP ending with a newline
> insert something with a TIMESTAMP ending with a newline
> insert something with a TIMESTAMP ending with a newline
> insert something with a TIMESTAMP ending with a newline
> commit transaction;
>
> Seen is this on a default postgres (no edb) install with default logprefix '%t'.
> May be it would be better to tokenize by '\nTIMESTAMP' instead.
I see the problem - but what about the first line of the file?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Timon | 2010-09-01 12:08:20 | fixed Russian translation |
Previous Message | Ashesh Vashi | 2010-09-01 08:42:23 | frmStatus: Assertion on linux and Segment Fault on Solaris |