Re: pg_get_triggerdef does not use the schema qualified procedure name

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: AJ Welch <awelch0100(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_get_triggerdef does not use the schema qualified procedure name
Date: 2019-09-26 22:47:31
Message-ID: 12993.1569538051@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

AJ Welch <awelch0100(at)gmail(dot)com> writes:
> I noticed that pg_get_triggerdef doesn't seem to use the schema qualified
> name of procedures/functions. Is it supposed to? Is there a way to get it
> to?

Generally the policy of such functions is to schema-qualify names that
wouldn't be found in the current search_path. So you could get what
you want by setting a restrictive search_path beforehand, maybe just ''.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message keisuke kuroda 2019-09-27 01:50:46 pg12 rc1 on CentOS8 depend python2
Previous Message AJ Welch 2019-09-26 20:01:57 pg_get_triggerdef does not use the schema qualified procedure name