On Tue, 2013-12-03 at 08:44 -0500, Stephen Frost wrote:
> * Tom Lane (t...@sss.pgh.pa.us) wrote:
> > > On 3 December 2013 02:02, Dimitri Fontaine <dimi...@2ndquadrant.fr> wrote:
> > > ISTM that the real solution to this particular problem is to decouple
> > > the extensions that are currently in contrib from a specific postgres
> > > version.
> >
> > "Problem"? It's not a bug that you get hstore 1.2 when you dump from 9.2
> > and reload into 9.3; that's a feature. You wanted an upgrade, presumably,
>
> I don't buy this argument at *all* and it's not going to fly when we've
> got multiple versions of an extension available concurrently.
It seems there's a use case for both behaviors; perhaps we should
include it in the control information?
preserve_version_on_dump (boolean)
FWIW, I find the current behavior surprising when in the mindset of a
SQL extension. But it makes sense for things more closely tied to the
backend.
Regards,
Jeff Davis
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
