Re: 2.7.2 still problem with readonly/autocommit, was: Changing set_session implementation

From: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
To: psycopg(at)postgresql(dot)org
Subject: Re: 2.7.2 still problem with readonly/autocommit, was: Changing set_session implementation
Date: 2017-10-01 13:50:18
Message-ID: 20171001135018.srsnlqjr7pgeuzbv@hermes.hilbert.loc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg

On Sun, Oct 01, 2017 at 02:42:33PM +0100, Daniele Varrazzo wrote:

>> I wonder whether there is any news regarding the bug reported
>> below ?
>
> There is a bug open, no timescale for it. It will be dealt with when I
> have time, or earlier if anyone contributes a solution. In honesty it
> is not on top of my priority list: even considering the time I can
> devolve to free-software projects (which is only a fraction of my free
> time), I have more pressing issues in other project (pg_repack
> screwing up logical decoding...). And I'm sure not in the position to
> use time paid by my employer to fix this bug.
>
> https://github.com/psycopg/psycopg2/issues/580

Thank you for the clarification.

Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346

In response to

Browse psycopg by date

  From Date Subject
Next Message Allan Kamau 2017-10-18 14:10:51 _psycopg.cpython-36m-x86_64-linux-gnu.so: undefined symbol: ASN1_STRING_length
Previous Message Daniele Varrazzo 2017-10-01 13:42:33 Re: 2.7.2 still problem with readonly/autocommit, was: Changing set_session implementation