Re: deparsing utility commands - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: deparsing utility commands
Date
Msg-id 20150806025519.GK2441@postgresql.org
Whole thread Raw
In response to Re: deparsing utility commands  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: deparsing utility commands  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
Jim Nasby wrote:
> On 7/31/15 8:45 AM, Shulgin, Oleksandr wrote:

> >STATEMENT:  create view v1 as select * from t1 ;
> >ERROR:  operator does not exist: pg_catalog.oid = pg_catalog.oid at
> >character 52
> >HINT:  No operator matches the given name and argument type(s). You
> >might need to add explicit type casts.
> >QUERY:  SELECT * FROM pg_catalog.pg_rewrite WHERE ev_class = $1 AND
> >rulename = $2
> >CONTEXT:  PL/pgSQL function test_ddl_deparse() line 1 at FOR over SELECT
> >rows

> I'm not sure what test_ddl_deparse is doing, is that where the oid = oid is
> coming from?
> 
> It might be enlightening to replace = with OPERATOR(pg_catalog.=) and see if
> that works.

That worked, thanks!

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Raising our compiler requirements for 9.6
Next
From: Alvaro Herrera
Date:
Subject: Re: Freeze avoidance of very large table.