5 Commits (6c6e6f7fd3ffa984a202b910ef3237e26f9d3c2e)

Author	SHA1	Message	Date
Peter Eisentraut	5dff93638c	Make PL/Python tests more compatible with Python 3 ... This changes a bunch of incidentially used constructs in the PL/Python regression tests to equivalent constructs in cases where Python 3 no longer supports the old syntax. Support for older Python versions is unchanged.	16 years ago
Peter Eisentraut	9d9848668f	Split the plpython regression test into test cases arranged by topic, instead ... of the previous monolithic setup-create-run sequence, that was apparently inherited from a previous test infrastructure, but makes working with the tests and adding new ones weird.	16 years ago
Bruce Momjian	37f11c3081	This patch addresses the problem mentioned in the "process crash ... when a plpython function returns unicode" thread: http://archives.postgresql.org/pgsql-bugs/2005-06/msg00105.php In several places PL/Python was calling PyObject_Str() and then PyString_AsString() without checking if the former had returned NULL to indicate an error. PyString_AsString() doesn't expect a NULL argument, so passing one causes a segmentation fault. This patch adds checks for NULL and raises errors via PLy_elog(), which prints details of the underlying Python exception. The patch also adds regression tests for these checks. All tests pass on my Solaris 9 box running HEAD and Python 2.4.1. In one place the patch doesn't call PLy_elog() because that could cause infinite recursion; see the comment I added. I'm not sure how to test that particular case or whether it's even possible to get an error there: the value that the code should check is the Python exception type, so I wonder if a NULL value "shouldn't happen." This patch converts NULL to "Unknown Exception" but I wonder if an Assert() would be appropriate. The patch is against HEAD but the same changes should be applied to earlier versions because they have the same problem. The patch might not apply cleanly against earlier versions -- will the committer take care of little differences or should I submit different versions of the patch? Michael Fuhr	20 years ago
Tom Lane	59ee9448a8	Remove read_file/write_file tests. These were originally intended to ... *fail*, to test that plpython didn't allow untrusted operations. When we changed plpython to plpythonu because python didn't actually have a secure sandbox mode, someone (probably me :-() misinterpreted the tests as checking whether Python's file I/O works. Which is a stupid thing for us to be testing. Remove it so we don't clutter the filesystem with random temporary files.	21 years ago
Tom Lane	0ff7a2c2ad	Convert the existing regression test scripts for the various optional ... PLs to use the standard pg_regress infrastructure. No changes in the tests themselves. Andrew Dunstan	21 years ago
Bruce Momjian	afb17d912b	> I've worked with the Pl/Python code in the past and will see about removing ... > rexec and making it an untrusted language. Last time I looked, it didn't > look particularly difficult. I've set aside some time next week, so stay > tuned. Attached is a patch that removes all of the RExec code from plpython from the current PostgreSQL CVS. In addition, plpython needs to be changed to an untrusted language in createlang. Please let me know if there are any problems. Kevin Jacobs	23 years ago
Tom Lane	1ca717f377	plpython security and error handling fixes, from ... Kevin Jacobs and Brad McLean.	24 years ago
Bruce Momjian	0bef7ba549	Add plpython code.	25 years ago