Re: [bug fix] pg_ctl always uses the same event source - Mailing list pgsql-hackers

From MauMau
Subject Re: [bug fix] pg_ctl always uses the same event source
Date
Msg-id E5E384918A6742F38C15D61724433240@maumau
Whole thread Raw
In response to Re: [bug fix] pg_ctl always uses the same event source  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [bug fix] pg_ctl always uses the same event source
List pgsql-hackers
From: "Magnus Hagander" <magnus@hagander.net>
> Not having looked at it in detail yet, but this seems to completely remove
> the default value. What happens if the error that needs to be logged is 
> the
> one saying that it couldn't exec postgres to find out the value in the
> config file? AFAICT it's going to try to register an eventsource with
> whatever random garbage happens to be in the variable.

Thank you for commenting, Magnus san.
The variable is global and contains an empty string, so even in the unlikely 
situation where postgres -C fails, the event source simply becomes blank.

Regards
MauMau




pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: GIN improvements part 1: additional information
Next
From: "MauMau"
Date:
Subject: Re: Re: [RFC] Shouldn't we remove annoying FATAL messages from server log?