Re: custom parameters cannot be removed once set - Mailing list pgsql-hackers

From Joe Conway
Subject Re: custom parameters cannot be removed once set
Date
Msg-id 56842710.3010108@joeconway.com
Whole thread Raw
In response to custom parameters cannot be removed once set  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
On 12/30/2015 10:36 AM, Joe Conway wrote:
> A side issue is that it would be nice if there were a way to check for a
> custom parameter value without getting an error if it does not exist.
> There is a missing_ok option to GetConfigOptionByName(), but we
> currently don't expose it from SQL. I'd like to add a variant of
> current_setting() with a second argument for missing_ok. Objections?

Nevermind this part -- I guess someone already beat me to it :-)

Joe

--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: custom parameters cannot be removed once set
Next
From: Alvaro Herrera
Date:
Subject: Re: Some 9.5beta2 backend processes not terminating properly?