From: Kevin Kempter <kevink@consistentstate.com>
To: pgsql-admin@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: pg_dump errors
Date: Thu, 3 Jun 2010 14:29:39 -0600
Message-ID: <201006031429.39396.kevink@consistentstate.com> (raw)
In-Reply-To: <7442.1275587101@sss.pgh.pa.us>
References: <201006031108.38937.kevink@consistentstate.com>
<201006031130.32033.kevink@consistentstate.com>
<7442.1275587101@sss.pgh.pa.us>
On Thursday 03 June 2010 11:45, Tom Lane wrote:
> Kevin Kempter <kevink@consistentstate.com> writes:
> > On Thursday 03 June 2010 11:18, Tom Lane wrote:
> >> Bizarre ... that command really oughtn't be invoking any non-builtin
> >> operator, but the OID is too high for a builtin. What do you get from
> >> "select 33639::regoperator"?
> >
> > postgres=# select 33639::regoperator
> > postgres-# ;
> > regoperator
> > ----------------
> > abc.=(oid,oid)
> > (1 row)
>
> So where did that come from, and why is it defined incorrectly?
> (Evidently it's marked oprcanhash but there is no associated hash
> opclass.) I can hardly see a reason to define your own oid equality
> operator, much less a wrong one ...
>
> regards, tom lane
I dont know where it came from. I havent intentionally defined any classes, or
anything like this. However this is a dev instance so maybe something went
wrong at some point.
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: kevink@consistentstate.com, tgl@sss.pgh.pa.us
Subject: Re: pg_dump errors
In-Reply-To: <201006031429.39396.kevink@consistentstate.com>
* 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