Re: Re: [COMMITTERS] pgsql: Allow pg_regress to be run outside the build tree.

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Allow pg_regress to be run outside the build tree.
Date: 2008-10-02 14:29:04
Message-ID: 48E4DAB0.5090307@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Tom Lane wrote:
>> I think the right fix would be to convert those .sql files to
>> input/*.source files and have pg_regress substitute the absolute
>> directory names in them, like it is done for the backend.
>
> Ugh. I don't think it's acceptable to make contrib modules have to do
> that. Even if we fix all the ones in core, what of other people relying
> on the pgxs infrastructure?

Yeah, true. Maybe copy the data directory over, but let pg_regress do it?

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-10-02 14:33:27 Re: Re: [COMMITTERS] pgsql: Allow pg_regress to be run outside the build tree.
Previous Message User Fxjr 2008-10-02 14:00:07 npgsql - Npgsql2: Fixed misleading timeout error message.

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonah H. Harris 2008-10-02 14:30:17 Re: Block-level CRC checks
Previous Message Heikki Linnakangas 2008-10-02 14:27:15 Re: Block-level CRC checks