Re: BUG #15678: The postgresql.conf string does not define server behavior (default_transaction_isolation)

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: dhaenoor(at)yandex(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15678: The postgresql.conf string does not define server behavior (default_transaction_isolation)
Date: 2019-03-08 18:36:46
Message-ID: CAKFQuwarbfCNH4ySr0GLdPFQBJWOED8o29-3nK=LnxQpjBkwqg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Mar 8, 2019 at 11:11 AM PG Bug reporting form
<noreply(at)postgresql(dot)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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Дуотт Даэнур 2019-03-08 18:41:15 Re: BUG #15678: The postgresql.conf string does not define server behavior (default_transaction_isolation)
Previous Message Дуотт Даэнур 2019-03-08 18:29:39 Re: BUG #15678: The postgresql.conf string does not define server behavior (default_transaction_isolation)