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

From Gregory S. Williamson
Subject Re: Setting search paths inside a function (plpgsql)
Date
Msg-id 71E37EF6B7DCC1499CEA0316A256832801D4B8A5@loki.wc.globexplorer.net
Whole thread Raw
In response to Setting search paths inside a function (plpgsql)  ("Gregory S. Williamson" <gsw@globexplorer.com>)
List pgsql-general
Doh !  Thanks for the insight.

Greg
-----Original Message-----
From:    Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent:    Wed 9/29/2004 8:40 AM
To:    Gregory S. Williamson
Cc:    pgsql-general@postgresql.org
Subject:    Re: [GENERAL] Setting search paths inside a function (plpgsql)
"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: "Geisler, Jim"
Date:
Subject: failure to restart postgresql service after improper shutdown
Next
From: Greg Stark
Date:
Subject: Re: Null comparisons (was Re: checksum)