On Wed, Apr 15, 2015 at 8:57 AM, David Steele <david@pgmasters.net> wrote:
> On 4/14/15 7:13 PM, Tatsuo Ishii wrote:
>> This patch does not apply cleanly due to the moving of pgbench (patch
>> to filelist.sgml failed).
>
> Thank you for pointing that out!
>
> Ironic that it was the commit directly after the one I was testing with
> that broke the patch. It appears the end of the last CF is a very bad
> time to be behind HEAD.
>
> Fixed in attached v8 patch.
Thank you for updating the patch!
I applied the patch and complied them successfully without WARNING.
I tested v8 patch with CURSOR case I mentioned before, and got
segmentation fault again.
Here are log messages in my environment,
=# select test();LOG: server process (PID 29730) was terminated by signal 11:
Segmentation fault
DETAIL: Failed process was running: select test();
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back
the current transaction and exit, because another server process
exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
FATAL: the database system is in recovery mode
I hope that these messages helps you to address this problem.
I will also try to address this.
Regards,
-------
Sawada Masahiko