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
--
Sent via psycopg mailing list (psycopg@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/psycopg