| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | johnsw(at)wardbrook(dot)com |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Missing OID rant |
| Date: | 2004-04-22 15:41:43 |
| Message-ID: | 7322.1082648503@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"John Sidney-Woollett" <johnsw(at)wardbrook(dot)com> writes:
> Please can someone explain why Postgres cannot recognize that objects
> (referenced by pl/pgsql functions) whose OID no longer exists could in
> fact be found (as new objects) if the function was reparsed and compiled
> again.
Criticism in the form of a patch would be useful.
> Whenever you delete an object, you locate any functions (or other objects)
> referencing that object's OID, and you mark them as invalid, and any
> subsequent objects that now refer to the newly invalidated object(s).
Yup, this is on the TODO list, and has been for awhile:
* Flush cached query plans when their underlying catalog data changes
> I don't know, but cannot believe that it would be hard to implement this,
Step right up ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2004-04-22 15:41:45 | Re: Unicode + LC_COLLATE |
| Previous Message | Tom Lane | 2004-04-22 15:32:57 | Re: [GENERAL] Restoring a Databases that features tserach2 |