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 -- Sent via pgadmin-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
