Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ellAv-0000xc-PO for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Feb 2018 00:43:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ellAt-0003df-I6 for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Feb 2018 00:43:51 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ellAs-0003cg-P7 for pgsql-hackers@lists.postgresql.org; Wed, 14 Feb 2018 00:43:51 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ellAl-0001qs-GP for pgsql-hackers@postgresql.org; Wed, 14 Feb 2018 00:43:49 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 0A1A821A2A; Tue, 13 Feb 2018 19:43:42 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Tue, 13 Feb 2018 19:43:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; 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-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=CLuVk4 fmXYtHpE8DwoCO+sg62OQJw58nve/Q9L5LKGE=; b=I5LMa95aAtlKk939z+29LN qKb66O+jB1BQtEmQYV9JDwHz/qJazIZ6lC/cv4n1iAR0GOzdWK//2c46aK3jWKYM 9YfQThhhKVSWKkf9Ue4IR/92x7zTlEro6eseD04kIxVACF/8mct3ZRZkRcGBUpr7 EyaP1G9v2INjfxsTYQLIinPsTDKK0upO4KaTUNyWehacXfOMStg0EYVBYhMC2F+Q yoEIa5Xr5xpRrAsZ8gRjBkbCsXU3VPLrsxEaK9V1prrlzfR+FKoR11gXUAccMWNf P0Oqzu0dugblXU7A0yZCU7NFI4aqbpbhjUCgDcJnVkDHqONqevQcxcwkVTnfNa9w == X-ME-Sender: 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 A97857E537; Tue, 13 Feb 2018 19:43:41 -0500 (EST) Subject: Re: master plpython check fails on Solaris 10 To: Marina Polyakova , pgsql-hackers@postgresql.org References: <156b989dbc6fe7c4d3223cf51da61195@postgrespro.ru> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <4a5588c7-9bcc-d5f5-b952-6b260467fc71@2ndquadrant.com> Date: Tue, 13 Feb 2018 19:43:41 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <156b989dbc6fe7c4d3223cf51da61195@postgrespro.ru> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2/13/18 05:40, Marina Polyakova wrote: > Binary search has shown that this failure begins with commit > 8561e4840c81f7e345be2df170839846814fa004 (Transaction control in PL > procedures.). On the previous commit > (b9ff79b8f17697f3df492017d454caa9920a7183) there's no > plpython_transaction test and plpython check passes. OK, can you get some kind of stack trace or other debugging information? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services