Обсуждение: BUG #15678: The postgresql.conf string does not define server behavior (default_transaction_isolation)

The following bug has been logged on the website:

Bug reference:      15678
Logged by:          Vasiliy Korotkikh
Email address:      dhaenoor@yandex.ru
PostgreSQL version: 11.2
Operating system:   Debian Stretch
Description:

In the configuration file of my server there is the following line:
default_transaction_isolation = 'serializable'

I make a query like this:
select current_setting('transaction_isolation')

It displays this message:
read committed

The isolation level inside the functions also does not correspond to the one
specified in the configuration file. 
For verification, I add into functions something like this: INSERT INTO
t1(textval) VALUES (current_setting('transaction_isolation'));

Also I used next query: ALTER ROLE ALL IN DATABASE mydb SET
default_transaction_isolation TO 'serializable';



P.S. If in the future you want to get more sensible error reports, then you
should think about a few examples. People understand examples better than
lengthy documentation descriptions.

On 2019-03-08 17:38:33 +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      15678
> Logged by:          Vasiliy Korotkikh
> Email address:      dhaenoor@yandex.ru
> PostgreSQL version: 11.2
> Operating system:   Debian Stretch
> Description:        
> 
> In the configuration file of my server there is the following line:
> default_transaction_isolation = 'serializable'

Did you reload the configuration after making that change? SELECT
pg_reload_conf();

Greetings,

Andres Freund

On Fri, Mar 8, 2019 at 11:11 AM PG Bug reporting form
<noreply@postgresql.org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference:      15678

> P.S. If in the future you want to get more sensible error reports, then you
> should think about a few examples. People understand examples better than
> lengthy documentation descriptions.

Likewise a self-contained executable example makes diagnosing bug
reports considerably easier.  As Andres said this is likely a caching
issue related to when changed settings take effect after making a
physical change.

David J.