Re: BUG #6168: db_link may generate additional unformatted log entries in stderr

>> I've stumbled on a few entries in my stderr log where the line prefix where
>> missing. e.g.:
>>
>> 2011-08-08 13:12:16 CEST|4e3fc490.17bc|6076|foo|DETAIL: Returned type
>> character ...
>> 2011-08-08 13:12:16 CEST|4e3fc490.17bc|6076|foo|CONTEXT: PL/pgSQL
>> function "bm_ ...
>> 2011-08-08 13:12:16 CEST|4e3fc490.17bc|6076|foo|STATEMENT: Select
>> coalesce(colu ...
>> => NOTICE: table "sessions_summary_raw_20110815" does not exist, skipping
>> => NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index
>> "pk_sessions_s ...
>> => NOTICE: table "sessions_site_summary_raw_20110815" does not exist,
>> skipping
>>
>> NOTICE entries should moreover not be logged !
>>
>> Those entries are coming from db_link.
>>

>I guess your test case is looping back to the same Postgres instance?

Yes, I use db_link to trigger multithreading :)

>But frankly this is an enhancement request, not a bug. The entire point
>of the stderr logging mechanism is to capture random printouts to stderr
>that might happen in code called by the backend, and it's doing exactly
>what it's supposed to.

Thanks for the explanation, this issue has no impact on our application.

best regards,

Marc Mamin