Re: 'DROP INDEX' kills stored rpocedures - Mailing list pgsql-general

From Tom Lane
Subject Re: 'DROP INDEX' kills stored rpocedures
Date
Msg-id 12209.1049397442@sss.pgh.pa.us
Whole thread Raw
In response to Re: 'DROP INDEX' kills stored rpocedures  ("scott.marlowe" <scott.marlowe@ihs.com>)
List pgsql-general
Vlad Krupin <vlad@echospace.com> writes:
> So, if I first re-create indexes and then do a 'VACUUM ANALYZE' on the
> table where those indexes were dropped, it should discard the old cached
> plans and create a new one, right?

All you need do is start a new database session --- plans are never
cached for longer than the life of one backend process.

            regards, tom lane


pgsql-general by date:

Previous
From: Dennis Gearon
Date:
Subject: Re: Suggestion
Next
From: Network Administrator
Date:
Subject: Multiple References on one Foreign Key