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

From: Satoshi Nagayasu <snaga(at)uptime(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:19:52
Message-ID: 559DF668.1040606@uptime.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2015/07/09 13:06, Tom Lane wrote:
> 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?

To check settings of GUC variables from a shared preload
library.

For example, I'd like to print "WARNING ...." in _PG_init()
when some GUC variable is disabled on postmaster startup.

Regards,
--
NAGAYASU Satoshi <snaga(at)uptime(dot)jp>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2015-07-09 04:28:16 Re: PL/pgSQL, RAISE and error context
Previous Message Tom Lane 2015-07-09 04:06:13 Re: Fix to expose a GUC variable, Log_disconnections, to outside of postgres.c