pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Karl Denninger <karl@denninger.net>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Upgrade failure attempting to go to 12.0
Date: Wed, 23 Oct 2019 00:38:08 -0400
Message-ID: <28859.1571805488@sss.pgh.pa.us> (raw)
In-Reply-To: <f2cf0a78-55d2-9d6b-8cc6-69a7d12e63f6@denninger.net>
References: <f2cf0a78-55d2-9d6b-8cc6-69a7d12e63f6@denninger.net>

Karl Denninger <karl@denninger.net> writes:
> I think I've seen this before, but I can't figure out where the issue
> is.  The original database dates to way, way back when contrib/tsearch2
> was a loaded module instead of the functionality being part of the base
> system, and I suspect vestigal pieces are involved.

Yeah, that's what it looks like.  This:

> Command was: CREATE OPERATOR CLASS "public"."gist_tp_tsquery_ops"

is part of the old tsearch2 stuff, and you'll need to remove it from
the v10 installation before you can upgrade.

What I can't tell from this evidence is whether you'd ever converted
tsearch2 into an actual extension --- if you had, then "drop extension"
would be enough to get rid of it.  Otherwise, you need to consult a copy
of the old "uninstall_tsearch2.sql" script to find out what you ought to
get rid of.

If you have user tables or indexes that depend on the old tsearch2
objects, things get more complex :-( --- you'd want to update those
to depend on the newer core datatype and index opclasses before
you clean out the old ones.

			regards, tom lane





view thread (2+ messages)

Message-ID: <28859.1571805488@sss.pgh.pa.us>
Permalink:  ../28859.1571805488@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/28859.1571805488@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, karl@denninger.net, pgsql-admin@lists.postgresql.org
  Subject: Re: Upgrade failure attempting to go to 12.0
  In-Reply-To: <28859.1571805488@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox