From: Tom Lane <tgl@sss.pgh.pa.us>
To: pavna <daryani.bhawna@gmail.com>
cc: pgsql-admin@postgresql.org
Subject: Re: pg_restore error Command was: CREATE OPERATOR ~> ( PROCEDURE =
 plv8x.json_eval_ls,
In-reply-to: <1530896890067-0.post@n3.nabble.com>
References: <1530850361998-0.post@n3.nabble.com>
 <69178.1530894011@sss.pgh.pa.us> <1530896890067-0.post@n3.nabble.com>
Comments: In-reply-to pavna <daryani.bhawna@gmail.com>
	message dated "Fri, 06 Jul 2018 10:08:10 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <69652.1530910299.1@sss.pgh.pa.us>
Date: Fri, 06 Jul 2018 16:51:39 -0400
Message-ID: <69653.1530910299@sss.pgh.pa.us>
Precedence: bulk

pavna <daryani.bhawna@gmail.com> writes:
> Thanks Tom for your response! Is there a way to examine the backup to find
> what was missing?  

Well, it's whatever was the commutator for that operator.  Evidently it
got dropped somewhere along the way.

It's a bit curious that you have this situation, though.  AFAICS,
dropping an operator should result in clearing the oprcom link from
its commutator sibling.  Perhaps there's some sequence of operations
that that logic fails to handle?  It'd be interesting if you can show
a way to reproduce this case.

			regards, tom lane