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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Eugen Konkov <kes-kes(at)yandex(dot)ru>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BUG #15646: Inconsistent behavior for current_setting/set_config
Date: 2019-02-26 14:11:12
Message-ID: CAKFQuwbip=NhvYLsTLtWvFSQRnL9=w0J=pE6h5kjOHsHc2D8EQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Tuesday, February 26, 2019, Eugen Konkov <kes-kes(at)yandex(dot)ru> 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.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Sandeep Thakkar 2019-02-26 16:04:21 Re: BUG #15647: pgagent file missing
Previous Message PG Bug reporting form 2019-02-26 13:47:31 BUG #15657: `session_replication_role = replica` not respected by truncation

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2019-02-26 14:29:01 Re: No-rewrite timestamp<->timestamptz conversions
Previous Message Jim Finnerty 2019-02-26 14:07:42 Re: NOT IN subquery optimization