Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gm0TE-0007PJ-Ck for psycopg@arkaria.postgresql.org; Tue, 22 Jan 2019 18:08:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gm0TC-0001lo-A2 for psycopg@arkaria.postgresql.org; Tue, 22 Jan 2019 18:08:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gm0QC-0006hQ-4Y for psycopg@lists.postgresql.org; Tue, 22 Jan 2019 18:05:12 +0000 Received: from mail-lj1-x236.google.com ([2a00:1450:4864:20::236]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gm0QA-0001Nn-8S for psycopg@postgresql.org; Tue, 22 Jan 2019 18:05:11 +0000 Received: by mail-lj1-x236.google.com with SMTP id l15-v6so21449624lja.9 for ; Tue, 22 Jan 2019 10:05:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=nvbvFQrQX52aWCi6xDtuYWN66KRWfGsnijmqiyVbEwA=; b=YfHgEl9xNXuaH8+hGwN6g4/swZelgYZ6hk94YnOo/54rlPTJ4AMPkeq7QcmMWfFF/2 wRNZB7Ghip58XyuR1kQ45sXsVQC2VslwMU4N8+sVQ0VEDf1VU8MSZ8DfsAGjGuR0UT7C ul0hkilP+FF4CvSLRWbhDwrA+JSOxc9fuDGTmBEv88iRUkUl57LjZaoVyBxZRaZTn4mR MEatIx6fuA+E8J7csIaDzH6CncxtO0Px479PlslV4I4iaBrkxM6tAWDtvi9ONdgJpBQN aybgvqzgR2Hih/sb/rPCxSEqjVodoqFF8k2qkCEtjhDfRGqnJ2Zx2xA1AIiD6l1QCTf7 2wCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=nvbvFQrQX52aWCi6xDtuYWN66KRWfGsnijmqiyVbEwA=; b=Xbj6E0WLVzb7e3wotCR5b+xSrd8ec/bf+3RjTEHlJFdElgZBLbluC3k4nKn3kQl7Q3 fsdr94+zNL7cd+7bIINW7/4+0JZVfzAKMM6hGkrwUq1VpsnkRNWrjrNgoodnAWxV+Phi RTzfljc051xUbJ/qHLaXbG3u0QvdZnOb/kZq6OZk43jyQS0BBwRykdrwlcMYl9LnHLtM JIinLORmw/ugDVhWSKR5fsHQoVdvwxbz8sYMKUAcr4FNTlB/lZm5H27FuHGv7Cw+fu1v BrO7tKzKWW0iTodseKoUiJ8ZMO3Ds7ra5rBxP0u+ypphr27NLK1FlyzzuDfBJXAoc+hi fteQ== X-Gm-Message-State: AJcUukex/WIod3MaqVwpCLSM3Tlu9q5LPl/LKaKthhHhiERCdg4dfKhE LkBNWZlw2Fo+jDvt1o2efAiwqCPeVoQSiY53KDguFA== X-Google-Smtp-Source: ALg8bN44/nCuGbFONvpvi/sDUWG3G0rqlxWFmTbYRsKXsdP2WHhCQcoZHdn+P2hO1DKiTSub60APBvb9fgxnuYJZXeo= X-Received: by 2002:a2e:914b:: with SMTP id q11-v6mr9151430ljg.164.1548180309102; Tue, 22 Jan 2019 10:05:09 -0800 (PST) MIME-Version: 1.0 From: Daniele Varrazzo Date: Tue, 22 Jan 2019 18:04:57 +0000 Message-ID: Subject: Psycopg 2.7.7 released To: psycopg@postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello, I've almost completed everything I want to do for the release of psycopg 2.8. However I found some dodgy management of the cursor state while not holding the GIL: this could be the cause of errors such as double free (#384) and "no result to fetch" on select (#346) in multithread environments. As I don't have a reproducible failing case the best way to verify the fixes is to provide a package to the people who have reported the problems. Cheers -- Daniele