| 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 22:17:20 |
| Message-ID: | 14057.1049408240@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:
> - Also, it does not seem to affect just regular SELECT queries - only
> when they are wrapped in my stored procedure that returns a refcursor.
Queries in plpgsql functions and PREPAREd queries are the only ones that
save plans, AFAIR.
> An even better way to do it is to tell all planners to discard their
> cached plans if the the index they are relying on suddenly disappears.
When we get around to implementing this, it will be automatic, not based
on the user having to do something special.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mlw | 2003-04-03 22:19:13 | Re: [PERFORM] [HACKERS] OSS database needed for testing |
| Previous Message | Alvaro Herrera | 2003-04-03 22:15:40 | Re: Postgres Syslog |