From: | Thom Brown <thombrown(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: VACUUM messages without newlines |
Date: | 2010-06-01 15:34:38 |
Message-ID: | AANLkTinUqzInEKuuorXg54j6Dvg58k9KWrfKZCXI1oyg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1 June 2010 16:28, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Excerpts from Thom Brown's message of mar jun 01 11:16:33 -0400 2010:
>> This has annoyed me for some time, but it appears that in the VACUUM
>> log, the line which says...
>>
>> INFO: analyzing "%s.%s"
>>
>> ...( and appears in pgsql/src/backend/commands/analyze.c lines 282 and
>> 287 ) doesn't terminate with a newline, meaning the next message
>> appears immediately after it.
>
> The message pieces are sent separately. They are only crammed in a
> single line if the interface is using the old mechanism to extract error
> message info; anything built after cca. 2002 should be reading fields
> separately, and printing them in separate lines.
I see what you mean. I'm seeing this in the latest version of pgAdmin
III (1.10.3) so looks like it's not up-to-date in that respect.
Should report it as a pgAdmin problem then?
Thanks
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2010-06-01 15:45:57 | Re: dividing money by money |
Previous Message | Alvaro Herrera | 2010-06-01 15:30:54 | Re: dividing money by money |