On Tuesday, February 26, 2019, Eugen Konkov wrote:
> If I use 'false' then transaction will not have effect, because I set the
> value to session?
>
The current transaction is always affected. True meansonly; false causes
the change to persist beyond, for the life of the session.
Davis J.
Hello
Documentation has no description how 'false' value for 'is_local' parameter
interact with transaction
Do I understand correct?
https://www.postgresql.org/docs/11/functions-admin.html#FUNCTIONS-ADMIN-SET
>set_config sets the parameter setting_name to new_value. If is_local is true,
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
On 2/20/19 12:11 PM, Tom Lane wrote:
> Joe Conway writes:
>> On 2/20/19 11:10 AM, PG Bug reporting form wrote:
>>> But current behavior returns empty string instead of NULL (the initial
>>> value) after transaction is rolled back. When I restart session, NULL is
>>> returned again as it is
