Re: [HACKERS] Fix to expose a GUC variable, Log_disconnections, to outside of postgres.c

On 2015/07/09 15:30, Heikki Linnakangas wrote: > On 07/09/2015 07:19 AM, Satoshi Nagayasu wrote: >> >> On 2015/07/09 13:06, Tom Lane wrote: >>> Satoshi Nagayasu writes: I just found that Log_disconnections value has not been exposed to outside of postgres.c. Despite that, Log_conn

Re: [HACKERS] Fix to expose a GUC variable, Log_disconnections, to outside of postgres.c

On 07/09/2015 07:19 AM, Satoshi Nagayasu wrote: > > On 2015/07/09 13:06, Tom Lane wrote: >> Satoshi Nagayasu writes: >>> I just found that Log_disconnections value has not been >>> exposed to outside of postgres.c. >>> Despite that, Log_connections has already been exposed. >> >> Why would an ext

Re: [HACKERS] Fix to expose a GUC variable, Log_disconnections, to outside of postgres.c

On 2015/07/09 13:06, Tom Lane wrote: > Satoshi Nagayasu writes: >> I just found that Log_disconnections value has not been >> exposed to outside of postgres.c. >> Despite that, Log_connections has already been exposed. > > Why would an external module need to touch either one? To check settings

Re: [HACKERS] Fix to expose a GUC variable, Log_disconnections, to outside of postgres.c

Satoshi Nagayasu writes: > I just found that Log_disconnections value has not been > exposed to outside of postgres.c. > Despite that, Log_connections has already been exposed. Why would an external module need to touch either one? regards, tom lane -- Sent via pgsql-h

[HACKERS] Fix to expose a GUC variable, Log_disconnections, to outside of postgres.c

Hi, I just found that Log_disconnections value has not been exposed to outside of postgres.c. Despite that, Log_connections has already been exposed. So, I'd like to add attached fix to touch the Log_disconnections value in other modules. Any comments? Regards, -- NAGAYASU Satoshi commit afff