From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Feld, Michael (IMS)" <FeldM(at)imsweb(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade error regarding hstore operator |
Date: | 2016-04-06 23:01:04 |
Message-ID: | 4937.1459983664@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
"Feld, Michael (IMS)" <FeldM(at)imsweb(dot)com> writes:
> Thanks for the assist Tom. That worked for us. Noticing a different
> issue following the pg_upgrade. If we take a pg_dump of a database on
> this upgraded instance with the hstore extension and try to pg_restore
> it back up to the same instance we get the following errors
Those are the *only* errors you get? That seems rather odd. I could
believe something like this happening if, say, you had an "unpackaged"
(that is, pre-extensions) version of hstore lying about. But then
you'd probably get conflicts on all the hstore-related objects, not
only the opclasses.
In any case, by far the most likely explanation is that you're trying to
restore into a non-empty database, probably because you've put stuff into
template1 and are cloning the new database from there.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Moran | 2016-04-06 23:24:26 | Re: what database schema version management system to use? |
Previous Message | Kevin Burke | 2016-04-06 22:22:56 | Deadlock between VACUUM and ALTER TABLE commands |
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2016-04-06 23:15:59 | Re: PATCH: use foreign keys to improve join estimates v1 |
Previous Message | Petr Jelinek | 2016-04-06 22:51:58 | Re: VS 2015 support in src/tools/msvc |