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

From: Дуотт Даэнур <dhaenoor(at)yandex(dot)ru>
To: David G(dot) Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <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:41:15
Message-ID: 16924461552070475@myt5-9da6df248f4a.qloud-c.yandex.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

<div xmlns="http://www.w3.org/1999/xhtml"><div style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:15px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;text-align:start;text-transform:none;white-space:normal;background-color:rgb(255,255,255);"><div>Problem solved.</div><div>The reason was that I used pgcli.</div><div>When I use psql, everything works as it should.</div><div>I assume that pgcli chooses transaction isolation level by itself.</div></div><div style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:15px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;text-align:start;text-transform:none;white-space:normal;background-color:rgb(255,255,255);"> </div><div style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:15px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;text-align:start;text-transform:none;white-space:normal;background-color:rgb(255,255,255);"><a target="_blank" style="color:rgb(153,0,153);" rel="noopener noreferrer" href="https://www.sql.ru/forum/1310005/funkciya-v-pg11-2-ne-zapuskaetsya-s-urovnem-izolyacii-serializable">https://www.sql.ru/forum/1310005/funkciya-v-pg11-2-ne-zapuskaetsya-s-urovnem-izolyacii-serializable</a></div><div style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:15px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;text-align:start;text-transform:none;white-space:normal;background-color:rgb(255,255,255);"> </div><div style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:15px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;text-align:start;text-transform:none;white-space:normal;background-color:rgb(255,255,255);">Thank you!</div></div><div><br /></div><div><br /></div><div>08.03.2019, 22:36, "David G. Johnston" &lt;david(dot)g(dot)johnston(at)gmail(dot)com&gt;:</div><blockquote type="cite"><p>On Fri, Mar 8, 2019 at 11:11 AM PG Bug reporting form<br />&lt;<a href="mailto:noreply(at)postgresql(dot)org">noreply(at)postgresql(dot)org</a>&gt; wrote:<br /></p><blockquote><br /> The following bug has been logged on the website:<br /><br /> Bug reference: 15678<br /></blockquote><p><br /></p><blockquote> P.S. If in the future you want to get more sensible error reports, then you<br /> should think about a few examples. People understand examples better than<br /> lengthy documentation descriptions.<br /></blockquote><p><br />Likewise a self-contained executable example makes diagnosing bug<br />reports considerably easier. As Andres said this is likely a caching<br />issue related to when changed settings take effect after making a<br />physical change.<br /><br />David J.<br /></p></blockquote>

Attachment Content-Type Size
unknown_filename text/html 2.7 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message gmail Vladimir Koković 2019-03-08 18:46:45 Re: BUG #15653: pg_detoast_datum_packed problem
Previous Message David G. Johnston 2019-03-08 18:36:46 Re: BUG #15678: The postgresql.conf string does not define server behavior (default_transaction_isolation)