From: | "Steffen Kuhn" <pg(at)kuhnsteffen(dot)de> |
---|---|
To: | "Dave Page" <dpage(at)pgadmin(dot)org> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Serverlog |
Date: | 2010-09-01 05:50:57 |
Message-ID: | 20100901055057.8DD8A2C0100C@bmail01.one.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
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.
Regards Steffen
From | Date | Subject | |
---|---|---|---|
Next Message | Ashesh Vashi | 2010-09-01 08:42:23 | frmStatus: Assertion on linux and Segment Fault on Solaris |
Previous Message | Dave Page | 2010-08-31 21:19:20 | Re: Problem with insert - 1.12.0 RC1 |