| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | moshe(at)neadwerx(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: RESET does not work as described |
| Date: | 2019-06-27 10:54:46 |
| Message-ID: | 699b5ed3-2af8-6e2f-4231-006016720582@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 6/26/19 11:39 AM, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/bug-reporting.html
> Description:
>
> The initial value returned when current_setting() is passed an unset
> parameter is '<NULL>'.
> After a SET and a RESET, the value returned by current_setting() is ''.
> This causes an invalid cast when the value is cast to an integer, as it is
> expected to be.
> Tested on Postgres 10 in Linux.
This has been discussed fairly recently but the discussion died out:
https://www.postgresql.org/message-id/flat/15646-0d3caee9f6266f60%40postgresql.org
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql | 2019-06-27 22:02:03 | Somente Hoje Mega Oferta Magazine Luiza - Por Apenas R$ 999,00 Smart TV 4K LED 40 Samsung ou iPhone 6s Apple 32GB - APROVEITE! - [ 201946974672 ] |
| Previous Message | PG Doc comments form | 2019-06-26 15:39:39 | RESET does not work as described |