Re: pg_dump errors

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

On Thursday 03 June 2010 11:45, Tom Lane wrote:
> 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

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.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Gnanakumar 2010-06-04 05:05:45 Re: PITR Recovery Question
Previous Message Kevin Grittner 2010-06-03 18:14:36 Re: [ADMIN] Modificar tamaño de pg_xlog