Re: pg_regress inputdir - Mailing list pgsql-hackers

From Jorgen Austvik - Sun Norway
Subject Re: pg_regress inputdir
Date
Msg-id 48907F0D.5090401@sun.com
Whole thread Raw
In response to Re: pg_regress inputdir  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: pg_regress inputdir  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera wrote:
>> Today, using --inputdir in pg_regress does not work for any other value
>> than something that resolves to cwd, since it will write a file to
>> "./sql", but try to read the same file from "<inputdir>/sql".
>
> Maybe I'm missing something, but I don't see any reason why this is a
> scenario worth supporting.  What's the problem with cd'ing into the
> directory containing the tests?

I agree - cd or some symlinks to cover up that the --inputdir parameter
does not work if you set it to anything except the default is a workaround.

Do we also agree that if you set --inputdir to anything other than the
default, pg_regress will not work (will write a file to one folder, and
try to read the same file from another)?

And if we agree above - should we make setting --inputdir work (read and
write from/to same directory), remove the --inputdir parameter (since
setting it to anything different from default value doesn't work), or
keep it there (to confuse people)?

-J
--

Jørgen Austvik, Software Engineering - QA
Sun Microsystems Database Group

Attachment

pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: TABLE-function patch vs plpgsql
Next
From: Tom Lane
Date:
Subject: Re: Type Categories for User-Defined Types