I installed postgres 9.4.6 on my Windows 7 (64-bit) machine, and managed to create the plpython3u extension without a problem. I then restored an existing DB (created in postgres 9.3). The plpython3 functions restored without a hitch and can execute. However, as soon as I try to create a NEW plpython3 function on the db the postgres service terminates and does an auto-recovery. I then downgraded to postgres 9.4.4 and am still encountering the same issue. Example: When running the following code: "create function test() returns void as $$ plpy.notice( 'xxx' ); $$ language plpython3u" the following is generated in the log: " 2016-03-31 09:36:56 CAT LOG: server process (PID 6376) exited with exit code 3 2016-03-31 09:36:56 CAT DETAIL: Failed process was running: create function test() returns void as $$ plpy.notice( 'xxx' ); $$ language plpython3u 2016-03-31 09:36:56 CAT LOG: terminating any other active server processes 2016-03-31 09:36:56 CAT WARNING: terminating connection because of crash of another server process 2016-03-31 09:36:56 CAT 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. 2016-03-31 09:36:56 CAT HINT: In a moment you should be able to reconnect to the database and repeat your command. 2016-03-31 09:36:56 CAT WARNING: terminating connection because of crash of another server process 2016-03-31 09:36:56 CAT 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. 2016-03-31 09:36:56 CAT HINT: In a moment you should be able to reconnect to the database and repeat your command. 2016-03-31 09:36:56 CAT WARNING: terminating connection because of crash of another server process 2016-03-31 09:36:56 CAT 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. 2016-03-31 09:36:56 CAT HINT: In a moment you should be able to reconnect to the database and repeat your command. " I am guessing that my problem might have something to do with the fact that the plpython2u language is not installed on the DB - although I am not sure why it should it need it, when executing a plpython3 command. As I understand it, Postgres 9.4 accomodates both versions of python. However I have not been able to figure out how to load plpython2u onto the db. The postgres version I installed does not ship with plpython2.dll and I have not been able to get hold of a copy. ( Python 2.7 /3.2 and 3.3 are installed on my machine, and I am running postgre versions 9.2, 9.3 and 9.4.4 on different ports). -- View this message in context: http://postgresql.nabble.com/Postgres-9-4-4-9-4-6-plpython2-3-intallation-issues-on-a-Windows-7-machine-tp5896157.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
