Re: plpython crash - Mailing list pgsql-hackers

From Jan Urbański
Subject Re: plpython crash
Date
Msg-id 4E4B8CA7.3090900@wulczer.org
Whole thread Raw
In response to Re: plpython crash  (Jan Urbański <wulczer@wulczer.org>)
Responses Re: plpython crash
List pgsql-hackers
On 16/08/11 19:12, Jan Urbański wrote:
> On 16/08/11 19:07, Jean-Baptiste Quenot wrote:
>> Dear Jan,
>>
>> Sorry I typed the wrong git commands.  With latest plpython from
>> branch master I got the same gdb backtrace as reported before.  I
>> managed to wrap up a testcase that fails 100% of times on my setup:
>> https://gist.github.com/1149512
>>
>> Hope it crashes on your side too :-)
> 
> Awesome, it segfaults for me with HEAD ;)
> 
> Now it's just a simple matter of programming... I'll take a look at it
> this evening.

Found it, we're invalidating the compiled functions cache when input
composite arguments change, but not when output composite arguments
change and the function gets called with pointers to invalid I/O routines.

I'll have a patch ready soon.

Jan


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Enforcing that all WAL has been replayed after restoring from backup
Next
From: Fujii Masao
Date:
Subject: Re: Online base backup from the hot-standby