6 Commits (2aa84520b3508dda273b9bbffab7bf87f0d98bf8)

Author	SHA1	Message	Date
Peter Eisentraut	98afa68d93	Use C99 designated initializers for some structs ... These are just a few particularly egregious cases that were hard to read and write, and error prone because of many similar adjacent types. Discussion: https://www.postgresql.org/message-id/flat/4c9f01be-9245-2148-b569-61a8562ef190%402ndquadrant.com	8 years ago
Peter Eisentraut	70ec3f1f8f	PL/Python: Add cursor and execute methods to plan object ... Instead of plan = plpy.prepare(...) res = plpy.execute(plan, ...) you can now write plan = plpy.prepare(...) res = plan.execute(...) or even res = plpy.prepare(...).execute(...) and similarly for the cursor() method. This is more in object oriented style, and makes the hybrid nature of the existing execute() function less confusing. Reviewed-by: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>	9 years ago
Peter Eisentraut	eaed88ce12	Add function name to PyArg_ParseTuple() ... This causes the supplied function name to appear in any error message, making the error message friendlier and relieving us from having to provide our own in some cases.	9 years ago
Tom Lane	8c75ad436f	Fix memory leaks in PL/Python. ... Previously, plpython was in the habit of allocating a lot of stuff in TopMemoryContext, and it was very slipshod about making sure that stuff got cleaned up; in particular, use of TopMemoryContext as fn_mcxt for function calls represents an unfixable leak, since we generally don't know what the called function might have allocated in fn_mcxt. This results in session-lifespan leakage in certain usage scenarios, as for example in a case reported by Ed Behn back in July. To fix, get rid of all the retail allocations in TopMemoryContext. All long-lived allocations are now made in sub-contexts that are associated with specific objects (either pl/python procedures, or Python-visible objects such as cursors and plans). We can clean these up when the associated object is deleted. I went so far as to get rid of PLy_malloc completely. There were a couple of places where it could still have been used safely, but on the whole it was just an invitation to bad coding. Haribabu Kommi, based on a draft patch by Heikki Linnakangas; some further work by me	10 years ago
Peter Eisentraut	f9de1e9a96	PL/Python: Add argument names to function declarations ... For easier source reading	14 years ago
Peter Eisentraut	147c248254	Split plpython.c into smaller pieces ... This moves the code around from one huge file into hopefully logical and more manageable modules. For the most part, the code itself was not touched, except: PLy_function_handler and PLy_trigger_handler were renamed to PLy_exec_function and PLy_exec_trigger, because they were not actually handlers in the PL handler sense, and it makes the naming more similar to the way PL/pgSQL is organized. The initialization of the procedure caches was separated into a new function init_procedure_caches to keep the hash tables private to plpy_procedures.c. Jan Urbański and Peter Eisentraut	14 years ago