Re: [HACKERS] pg_regress input/output directory option
On Fri, Sep 30, 2011 at 12:37 AM, Robert Haas wrote: > On Wed, Sep 28, 2011 at 12:21 AM, Michael Paquier > 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
Re: [HACKERS] pg_regress input/output directory option
On Wed, Sep 28, 2011 at 12:21 AM, Michael Paquier 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
