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

• Re: Re: [COMMITTERS] pgsql: Allow pg_regress to be run outside the build tree. at 2008-10-02 13:28:24 from Tom Lane

Responses

• Re: Re: [COMMITTERS] pgsql: Allow pg_regress to be run outside the build tree. at 2008-10-02 14:33:27 from Tom Lane
• Re: Re: [COMMITTERS] pgsql: Allow pg_regress to be run outside the build tree. at 2008-10-03 07:29:35 from Bjorn Munch

pgsql-hackers by date

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

pgsql-committers by date

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