Re: pl/pgsql Plan Invalidation and search_path

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Stephen Frost" <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pl/pgsql Plan Invalidation and search_path
Date: 2008-03-26 02:07:18
Message-ID: b42b73150803251907iaa1169bndd41b966ff7b8ada@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 24, 2008 at 9:48 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> Add to pl/pgsql TODO:
>
> o Consider invalidating the cache or keeping seperate cached
> copies when search_path changes
>
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg01009.php

IMO, Tom's idea, namely to keep separate cache plans for various
search_path settings, is a much stronger proposal and should probably
get the 'todo'.

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-03-26 02:40:11 Re: pl/pgsql Plan Invalidation and search_path
Previous Message Tom Lane 2008-03-26 01:59:59 Re: Script binaries renaming