Re: Behavior of pg_catalog dependent on search_path: expected or bug?

 

This script worked the first time but then failed on reruns. After some investigation, I noticed that this was run as part of a larger script and a “search_path” was set. I was able to isolate a behavior that I am not able to understand, i.e., bug or expected behavior?

 

The code below fails:

 

SET search_path TO XXX;

select p.oid::regprocedure

  from pg_catalog.pg_proc p

  join pg_catalog.pg_namespace n on p.pronamespace = n.oid

 where p.oid::regprocedure::text='sample(anyelement)'

   and n.nspname = 'public'