Skip site navigation (1) Skip section navigation (2)

Re: pg_upgrade automatic testing

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade automatic testing
Date: 2011-09-03 14:24:40
Message-ID: 1315059883.11695.22.camel@vanquo.pezone.net (view raw or flat)
Thread:
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.


In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2011-09-03 14:35:41
Subject: Re: pgsql: Remove "fmgr.h" include in cube contrib --- caused crash on a Ge
Previous:From: Tom LaneDate: 2011-09-03 14:23:09
Subject: Re: pgsql: Remove "fmgr.h" include in cube contrib --- caused crash on a Ge

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group