postgresql/src/pl
Peter Eisentraut da265a8717 plpython: Streamline initialization
The initialization of PL/Python (the Python interpreter, the global
state, the plpy module) was arranged confusingly across different
functions with unclear and confusing boundaries.  For example,
PLy_init_interp() said "Initialize the Python interpreter ..." but it
didn't actually do this, and PLy_init_plpy() said "initialize plpy
module" but it didn't do that either.  After this change, all the
global initialization is called directly from _PG_init(), and the plpy
module initialization is all called from its registered initialization
function PyInit_plpy().

Reviewed-by: Chao Li <li.evan.chao@gmail.com>
Reviewed-by: Matheus Alcantara <matheusssilv97@gmail.com>
Reviewed-by: li carol <carol.li2025@outlook.com>
Reviewed-by: Kirill Reshke <reshkekirill@gmail.com>
Discussion: https://www.postgresql.org/message-id/f31333f1-fbb7-4098-b209-bf2d71fbd4f3%40eisentraut.org
2026-01-15 12:11:52 +01:00
..
plperl Update copyright for 2026 2026-01-01 13:24:10 -05:00
plpgsql Update copyright for 2026 2026-01-01 13:24:10 -05:00
plpython plpython: Streamline initialization 2026-01-15 12:11:52 +01:00
tcl Update copyright for 2026 2026-01-01 13:24:10 -05:00
Makefile Make distprep and *clean build targets recurse into all subdirectories. 2011-07-03 13:55:12 -04:00
meson.build Update copyright for 2026 2026-01-01 13:24:10 -05:00