Re: BUG #15646: Inconsistent behavior for current_setting/set_config - Mailing list pgsql-hackers

From Eugen Konkov
Subject Re: BUG #15646: Inconsistent behavior for current_setting/set_config
Date
Msg-id 356428520.20190226143539@yandex.ru
Whole thread Raw
In response to Re: BUG #15646: Inconsistent behavior for current_setting/set_config  (Joe Conway <mail@joeconway.com>)
Responses Re: BUG #15646: Inconsistent behavior for current_setting/set_config  (Eugen Konkov <kes-kes@yandex.ru>)
List pgsql-hackers
Hello,

Not sure I should open new issue or continue this one.

select set_config( 'my.some_conf', 'value', true );

does not issue warning if there is no transaction in progress.

I  faced into this problem when call to stored function which make use
of configurations. and missed that this function has no effect because
there is no transaction in progress

-- 
Best regards,
Eugen Konkov



pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Oddity with parallel safety test for scan/join target in grouping_planner
Next
From: Eugen Konkov
Date:
Subject: Re: BUG #15646: Inconsistent behavior for current_setting/set_config