Re: BUG #14649: Function Namespace Resolution Bug

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeremy Cowgar <jeremy(at)cowgar(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14649: Function Namespace Resolution Bug
Date: 2017-05-12 18:50:50
Message-ID: 5732.1494615050@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Jeremy Cowgar <jeremy(at)cowgar(dot)com> writes:
> Why does it find the initial function just fine in the public namespace, but the method it calls it can not find, which is 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeremy Cowgar 2017-05-12 19:16:49 Re: BUG #14649: Function Namespace Resolution Bug
Previous Message Jeremy Cowgar 2017-05-12 18:25:23 Re: BUG #14649: Function Namespace Resolution Bug