pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Marina Polyakova <m.polyakova@postgrespro.ru>
To: pgsql-hackers@postgresql.org
Subject: Re: master plpython check fails on Solaris 10
Date: Tue, 13 Feb 2018 19:43:41 -0500
Message-ID: <4a5588c7-9bcc-d5f5-b952-6b260467fc71@2ndquadrant.com> (raw)
In-Reply-To: <156b989dbc6fe7c4d3223cf51da61195@postgrespro.ru>
References: <156b989dbc6fe7c4d3223cf51da61195@postgrespro.ru>

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




view thread (7+ messages)  latest in thread

Message-ID: <4a5588c7-9bcc-d5f5-b952-6b260467fc71@2ndquadrant.com>
Permalink:  ../4a5588c7-9bcc-d5f5-b952-6b260467fc71@2ndquadrant.com/
Also on:    postgresql.org/message-id/4a5588c7-9bcc-d5f5-b952-6b260467fc71@2ndquadrant.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@2ndquadrant.com, m.polyakova@postgrespro.ru
  Subject: Re: master plpython check fails on Solaris 10
  In-Reply-To: <4a5588c7-9bcc-d5f5-b952-6b260467fc71@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox