Re: Setting search paths inside a function (plpgsql) - Mailing list pgsql-general

From Tom Lane
Subject Re: Setting search paths inside a function (plpgsql)
Date
Msg-id 29493.1096472430@sss.pgh.pa.us
Whole thread Raw
In response to Setting search paths inside a function (plpgsql)  ("Gregory S. Williamson" <gsw@globexplorer.com>)
List pgsql-general
"Gregory S. Williamson" <gsw@globexplorer.com> writes:
>         RAISE NOTICE ''doing name search for fips %'',p_fips;
>         env_str := ''SET search_path TO f'' || p_fips || '',public'';
>         EXECUTE env_str;
>         RAISE NOTICE ''did exec of <%>'',env_str;
>         FOR retrec IN
>                 SELECT o.gid,o.s_fips_cou,o.s_zip,o.s_ownername
>                 FROM parcel_owners o, parcel_owner_fti f
>                 WHERE f.string = p_srchstr AND f.id = o.orig_id ORDER BY 2,3,4
>                         LOOP

You'd have to use FOR-IN-EXECUTE to make this work the way you are
expecting.  As is, the plan for the SELECT is generated and cached
the first time through, and in the process the table references are
bound to specific tables in specific schemas.

            regards, tom lane

pgsql-general by date:

Previous
From: "Jonathan Villa"
Date:
Subject: Converting to Java date example
Next
From: "Net Virtual Mailing Lists"
Date:
Subject: Re: Postgres inherited table, some questions...