pg_regress input/output directory option

Started by Michael Paquierover 14 years ago3 messageshackers
Jump to latest
#1Michael Paquier
michael@paquier.xyz

Hi all,

Why are there no options in_regress to specify the directory where input and
output data are located?
Such options would bring more flexibility when running regressions without
make check/installcheck for an external application.
Is there a particular reason for that? Or do you think that pg_regress
should be only used with make check?

Regards,
--
Michael Paquier
http://michael.otacoo.com

#2Robert Haas
robertmhaas@gmail.com
In reply to: Michael Paquier (#1)
Re: pg_regress input/output directory option

On Wed, Sep 28, 2011 at 12:21 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:

Why are there no options in_regress to specify the directory where input and
output data are located?
Such options would bring more flexibility when running regressions without
make check/installcheck for an external application.
Is there a particular reason for that? Or do you think that pg_regress
should be only used with make check?

It has --inputdir and --outputdir - is that not what you need?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

#3Michael Paquier
michael@paquier.xyz
In reply to: Robert Haas (#2)
Re: pg_regress input/output directory option

On Fri, Sep 30, 2011 at 12:37 AM, Robert Haas <robertmhaas@gmail.com> wrote:

On Wed, Sep 28, 2011 at 12:21 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:

Why are there no options in_regress to specify the directory where input

and

output data are located?
Such options would bring more flexibility when running regressions

without

make check/installcheck for an external application.
Is there a particular reason for that? Or do you think that pg_regress
should be only used with make check?

It has --inputdir and --outputdir - is that not what you need?

Yes thanks.

Regards,

Michael