Horton

Re: pg_upgrade automatic testing

Peter Eisentraut <peter_e@gmx.net>

View thread
From: Peter Eisentraut <peter_e@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>, Bruce Momjian <bruce@momjian.us>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-09-03T14:24:40Z
Lists: pgsql-hackers 
On fre, 2011-09-02 at 19:49 -0400, Tom Lane wrote:
> The only one that's problematic is pg_regress.so; contrib modules are
> already installed in $libdir.  I still think that installing
> pg_regress.so in $libdir may be the most reasonable solution, assuming
> that the delta involved isn't too great.  Yeah, we would have to
> back-patch the changes into every release branch we want to test
> upgrading from, but how risky is that really?  The *only* thing it
> affects is the regression tests.

Or maybe make use of dynamic_library_path.