Re: Issue with plpython write_file and read_file tests - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Issue with plpython write_file and read_file tests
Date
Msg-id 25828.1119300877@sss.pgh.pa.us
Whole thread Raw
In response to Issue with plpython write_file and read_file tests  ("Jim C. Nasby" <decibel@decibel.org>)
List pgsql-hackers
"Jim C. Nasby" <decibel@decibel.org> writes:
> Setting up the buildfarm on a machine I've discovered an issue with the
> plpython write_file and read_file tests. The problem can be seen at
> http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=platypus&dt=2005-06-20%2018:15:00
> The specific issue is that the test doesn't clean up after itself,
> leaving /tmp/plpython behind. This raised it's ugly head when I tested
> the buildfarm stuff as one user and then switched to using a different
> user.

> What would be the best way to handle this?

Remove that test altogether.  It'd only be sane in a test of a trusted
plpython language, which we have not got now.  I would imagine that the
original writer of the code never expected the write to succeed at all.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: index selection by query planner
Next
From: Alvaro Herrera
Date:
Subject: Re: pg_locks view versus prepared transactions