Re: Enhancement Idea - Expose the active value of a parameter in pg_settings

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Greg Clough <greg(dot)clough(at)ipreo(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Enhancement Idea - Expose the active value of a parameter in pg_settings
Date: 2018-05-25 16:18:29
Message-ID: CA+TgmoZ4mV0b2O76PbJCZ4ko7oV5puFz49KvVE4FFc0CoyvDtg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 25, 2018 at 12:14 PM, Greg Clough <greg(dot)clough(at)ipreo(dot)com> wrote:
> Many thanks for the quick consideration, even if it's ultimately a rejection. Figuring out some SQL that will work across all platforms, versions, and compile-time options will be "fun", but I'm up for a challenge.

Why would you need different SQL for this on different platforms or
with different compile-time options?

I agree that there could be some variation across major versions, but
I don't think there's a lot.

BTW, posting to a public mailing list with a giant blob of legalese
about confidential information in your signature is kind of silly.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Reiss 2018-05-25 16:53:17 Re: Performance regression with PostgreSQL 11 and partitioning
Previous Message Tom Lane 2018-05-25 16:16:41 We still claim "cannot begin/end transactions in PL/pgSQL"