pgsql: Remove read_file/write_file tests.

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Remove read_file/write_file tests.
Date: 2005-06-20 21:14:01
Message-ID: 20050620211401.BD241528B4@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
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.

Modified Files:
--------------
pgsql/src/pl/plpython/expected:
plpython_error.out (r1.1 -> r1.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/expected/plpython_error.out.diff?r1=1.1&r2=1.2)
plpython_function.out (r1.1 -> r1.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/expected/plpython_function.out.diff?r1=1.1&r2=1.2)
pgsql/src/pl/plpython/sql:
plpython_error.sql (r1.1 -> r1.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/sql/plpython_error.sql.diff?r1=1.1&r2=1.2)
plpython_function.sql (r1.1 -> r1.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/sql/plpython_function.sql.diff?r1=1.1&r2=1.2)

Browse pgsql-committers by date

  From Date Subject
Next Message User Andrewd 2005-06-20 22:15:53 pgbuildfarm - client-code: .
Previous Message Tom Lane 2005-06-20 20:45:13 pgsql: plpgsql's exec_assign_value() freed the old value of a variable