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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Satoshi Nagayasu <snaga(at)uptime(dot)jp>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix to expose a GUC variable, Log_disconnections, to outside of postgres.c
Date: 2015-07-09 04:06:13
Message-ID: 16300.1436414773@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Satoshi Nagayasu <snaga(at)uptime(dot)jp> 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Satoshi Nagayasu 2015-07-09 04:19:52 Re: Fix to expose a GUC variable, Log_disconnections, to outside of postgres.c
Previous Message Satoshi Nagayasu 2015-07-09 03:52:20 Fix to expose a GUC variable, Log_disconnections, to outside of postgres.c