Re: 'DROP INDEX' kills stored rpocedures

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Vlad Krupin <vlad(at)echospace(dot)com>
Cc: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: 'DROP INDEX' kills stored rpocedures
Date: 2003-04-03 19:17:22
Message-ID: 12209.1049397442@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Vlad Krupin <vlad(at)echospace(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Network Administrator 2003-04-03 19:18:51 Multiple References on one Foreign Key
Previous Message Dennis Gearon 2003-04-03 19:16:55 Re: [GENERAL] Suggestion