Re: current_setting returns 'unset'

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: current_setting returns 'unset'
Date: 2006-01-10 16:26:50
Message-ID: 510.1136910410@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Moreover, the unset state shouldn't exist at all. No parameter can behave
> reasonably if unset behaved differently from an empty string. Explicitly
> assigning an unset state doesn't work. So it seems that for all external
> communication, an unset string parameter should simply display the empty
> string.

I wouldn't object to that, but my recollection is that that was once the
behavior, and somebody insisted it was bad.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Harald Fuchs 2006-01-10 16:52:54 Re: Question about Postgresql time fields(possible bug)
Previous Message Dave Page 2006-01-10 15:56:34 Re: Question about Postgresql time fields(possible bug)