Re: Testing truthiness of GUC variables?

From: Abelard Hoffman <abelardhoffman(at)gmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Testing truthiness of GUC variables?
Date: 2014-09-15 06:20:41
Message-ID: CACEJHMhpz2gNP2MhWYYq8Uj0sBt1b25Nkq2ksLsPTrAu+KOzGQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Sep 14, 2014 at 11:17 PM, Abelard Hoffman <abelardhoffman(at)gmail(dot)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 on, off, true, false, yes, no, 1, 0 (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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Marti Raudsepp 2014-09-15 09:59:46 Re: Why isn't Java support part of Postgresql core?
Previous Message Abelard Hoffman 2014-09-15 06:17:42 Testing truthiness of GUC variables?