Re: pg_dump errors

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Kempter <kevink(at)consistentstate(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_dump errors
Date: 2010-06-03 17:45:01
Message-ID: 7442.1275587101@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Kevin Kempter <kevink(at)consistentstate(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Kevin Grittner 2010-06-03 18:14:36 Re: [ADMIN] Modificar tamaño de pg_xlog
Previous Message Kevin Kempter 2010-06-03 17:30:31 Re: pg_dump errors