Re: [HACKERS] Transactions involving multiple postgres foreignservers

Hi Sawada-san,

Thank you for reviewing!

I think this is a bug of pg_fdw_resolver contrib module. I had
forgotten to change the SQL executed by pg_fdw_resolver process.
Attached latest version 002 patch.

As previous version patch conflicts to current HEAD, attached updated
version patches. Also I fixed some bugs in pg_fdw_xact_resolver and
added some documentations.
Please review it.

Thank you updating the patches.

I have applied patches on Postgres HEAD.
I have created the postgres=fdw extension in PostgreSQL and then I got segmentation fault.
Details:
=# 2017-01-26 17:52:56.156 JST [3411] LOG:  worker process: foreign transaction resolver launcher (PID 3418) was terminated by signal 11: Segmentation fault
2017-01-26 17:52:56.156 JST [3411] LOG:  terminating any other active server processes
2017-01-26 17:52:56.156 JST [3425] WARNING:  terminating connection because of crash of another server process
2017-01-26 17:52:56.156 JST [3425] 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.
2017-01-26 17:52:56.156 JST [3425] HINT:  In a moment you should be able to reconnect to the database and repeat your command.

Is this a bug?

Regards,
Vinayak Pokale
NTT Open Source Software Center