From: | Jorgen Austvik - Sun Norway <Jorgen(dot)Austvik(at)Sun(dot)COM> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_regress inputdir |
Date: | 2008-07-30 14:47:41 |
Message-ID: | 48907F0D.5090401@sun.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 | Content-Type | Size |
---|---|---|
jorgen_austvik.vcf | text/x-vcard | 418 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-07-30 14:50:49 | Re: Type Categories for User-Defined Types |
Previous Message | Hannu Krosing | 2008-07-30 14:30:51 | Re: TABLE-function patch vs plpgsql |