Re: BUG #15646: Inconsistent behavior for current_setting/set_config

From: Eugen Konkov <kes-kes(at)yandex(dot)ru>
To: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: BUG #15646: Inconsistent behavior for current_setting/set_config
Date: 2019-02-26 12:35:39
Message-ID: 356428520.20190226143539@yandex.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Eugen Konkov 2019-02-26 12:48:46 Re: BUG #15646: Inconsistent behavior for current_setting/set_config
Previous Message Prakash Ramakrishnan 2019-02-26 10:06:35 Re: BUG #15648: oracle_fdw extension not able to create

Browse pgsql-hackers by date

  From Date Subject
Next Message Eugen Konkov 2019-02-26 12:48:46 Re: BUG #15646: Inconsistent behavior for current_setting/set_config
Previous Message Etsuro Fujita 2019-02-26 12:25:34 Oddity with parallel safety test for scan/join target in grouping_planner