Re: [BUGS] BUG #14649: Function Namespace Resolution Bug - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [BUGS] BUG #14649: Function Namespace Resolution Bug
Date
Msg-id 5732.1494615050@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUGS] BUG #14649: Function Namespace Resolution Bug  (Jeremy Cowgar <jeremy@cowgar.com>)
Responses Re: [BUGS] BUG #14649: Function Namespace Resolution Bug  (Jeremy Cowgar <jeremy@cowgar.com>)
List pgsql-bugs
Jeremy Cowgar <jeremy@cowgar.com> writes:
> Why does it find the initial function just fine in the public namespace, but the method it calls it can not find,
whichis in the same namespace as the calling function? 

pg_dump is smart enough to schema-qualify that one.  If you look at
the actual dump output for the table, it looks like

SET search_path = g, pg_catalog;
...
CREATE TABLE people (   id integer NOT NULL,   name character varying(50) NOT NULL,   CONSTRAINT people_name_check
CHECK(public.has_content((name)::text)) 
);

However, editing the body text of your function is beyond pg_dump's
competence.
        regards, tom lane


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Jeremy Cowgar
Date:
Subject: Re: [BUGS] BUG #14649: Function Namespace Resolution Bug
Next
From: Jeremy Cowgar
Date:
Subject: Re: [BUGS] BUG #14649: Function Namespace Resolution Bug