Re: Serverlog
От | Dave Page |
---|---|
Тема | Re: Serverlog |
Дата | |
Msg-id | AANLkTik6G-hoBK85XiXR8k_9qj=SHftPK27Kf6MrbY5G@mail.gmail.com обсуждение исходный текст |
Ответ на | Serverlog ("Steffen Kuhn" <pg@kuhnsteffen.de>) |
Список | pgadmin-hackers |
On Wed, Sep 1, 2010 at 6:50 AM, Steffen Kuhn <pg@kuhnsteffen.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
В списке pgadmin-hackers по дате отправления: