Re: 'DROP INDEX' kills stored rpocedures

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

"scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com> writes:
> Don't make assumptions like that. In postgresql, DDL is transactionable.

I think his actual problem is that plpgsql cached a query plan for some
command while the index was in place, and then on a later re-execution
of the function, it tried to re-use the cached plan. This is a general
problem that we know we need to fix sooner or later --- cached plans
need to be invalidated when there are DDL changes to the underlying
tables, views, etc.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-04-03 19:11:13 Re: RelationBuildDesc Notice (corrupt DB?)
Previous Message Stephan Szabo 2003-04-03 18:57:44 Re: updating table field whenever other table field changes