Re: Testing truthiness of GUC variables? - Mailing list pgsql-general

From Abelard Hoffman
Subject Re: Testing truthiness of GUC variables?
Date
Msg-id CACEJHMhpz2gNP2MhWYYq8Uj0sBt1b25Nkq2ksLsPTrAu+KOzGQ@mail.gmail.com
Whole thread Raw
In response to Testing truthiness of GUC variables?  (Abelard Hoffman <abelardhoffman@gmail.com>)
Responses Re: Testing truthiness of GUC variables?
List pgsql-general


On Sun, Sep 14, 2014 at 11:17 PM, Abelard Hoffman <abelardhoffman@gmail.com> wrote:
If I set a custom GUC variable to a boolean value, such as:

  SET myapp.audit = 'on';

is there a way to test it for truthiness in the same way the standard built-in variables are? IOW, the docs say a boolean can be written as:

Boolean values can be written as onofftruefalseyesno10 (all case-insensitive) or any unambiguous prefix of these.


Sorry, hit send too soon. I meant to ask, is there a built-in function I can call, given the value from current_setting('myapp.audit'), that will test it using the same logic?

pgsql-general by date:

Previous
From: Abelard Hoffman
Date:
Subject: Testing truthiness of GUC variables?
Next
From: Marti Raudsepp
Date:
Subject: Re: Why isn't Java support part of Postgresql core?