Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bmOto-0006Cl-Fr for pgsql-docs@arkaria.postgresql.org; Tue, 20 Sep 2016 17:32:04 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bmOto-0003v2-34 for pgsql-docs@arkaria.postgresql.org; Tue, 20 Sep 2016 17:32:04 +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_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bmOtn-0003tv-Hd for pgsql-docs@postgreSQL.org; Tue, 20 Sep 2016 17:32:03 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bmOtk-0003zH-GY for pgsql-docs@postgreSQL.org; Tue, 20 Sep 2016 17:32:03 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 182442070B; Tue, 20 Sep 2016 13:31:59 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Tue, 20 Sep 2016 13:31:59 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=uAH/QpAMomi2SZP L1uvHqoey5UU=; b=tmGRPWphHchBtwJm/TaThRHws8/g+NsN0qzd+WQ+OHquiKI ENHN1uN9/9fyoGJbGZavDj/FNQwsYAk+K9tQ5SnRS2VIxeUaQ8Ro6nD0mMVG8VDa 01+40XNHphgH9yPef9m64wMbU4wUwPIl74+y2jN42gHHB7cxuZjGrfH7Ni30= X-Sasl-enc: wN4wOu3lCyGprTL4NhqLc47ygk2KU0g0fKp/dFpyaTkv 1474392718 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id BDA32CCE96; Tue, 20 Sep 2016 13:31:58 -0400 (EDT) Subject: Re: Obsolete warning on Python 2.4 To: Heikki Linnakangas , pgsql-docs References: <85e377b2-d459-396e-59b1-115548bbc059@iki.fi> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <04f81c77-ee67-5604-4297-ecd8969d3cf3@2ndquadrant.com> Date: Tue, 20 Sep 2016 13:31:58 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <85e377b2-d459-396e-59b1-115548bbc059@iki.fi> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On 9/19/16 1:21 AM, Heikki Linnakangas wrote: > The docs say: >> Warning >> >> Due to Python bug #1483133, some debug versions of Python 2.4 >> (configured and compiled with option --with-pydebug) are known to >> crash the PostgreSQL server when using an iterator to return a set >> result. Unpatched versions of Fedora 4 contain this bug. It does not >> happen in production versions of Python or on patched versions of >> Fedora 4. > > That seems uninteresting to anyone in 2016. Any objections to removing it? We're still maintaining compatibility with Python 2.4 and the bug apparently still exists, so I would perhaps keep it until we kill support for Python 2.4. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs