Re: master plpython check fails on Solaris 10

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

To: Marina Polyakova <m.polyakova@postgrespro.ru>, pgsql-hackers@postgresql.org

Date: 2018-02-14T00:43:41Z

Lists: pgsql-hackers

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

Commits

Add an assertion that we don't pass NULL to snprintf("%s").
- 0c62356cc877 11.0 landed
Fix broken logic for reporting PL/Python function names in errcontext.
- e748e902def4 11.0 landed
- db1c597f3c33 9.5.12 landed
- bd871863787b 9.4.17 landed
- 457e9e88e357 9.3.22 landed
- 4081e1136178 10.3 landed
- 0a2381d13f77 9.6.8 landed
Fix typo
- ebdb42a0d6a6 11.0 cited
Transaction control in PL procedures
- 8561e4840c81 11.0 cited
Fix docs typo
- b9ff79b8f176 11.0 cited
plpython security and error handling fixes, from
- 1ca717f377c7 7.2.1 cited