From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jan Wieck <janwieck(at)yahoo(dot)com> |
Cc: | jm(dot)poure(at)freesurf(dot)fr, Andrew Sullivan <andrew(at)libertyrms(dot)info>, PostgreSQL general list <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Feature enhancement request : use of libgda |
Date: | 2002-02-11 20:02:38 |
Message-ID: | 15118.1013457758@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Jan Wieck <janwieck(at)yahoo(dot)com> writes:
> Now it might be possible to tell your function handler to
> recompile that function at the next call without changing the
> OID, but how do you tell the function handlers in all the
> other concurrently running backends to do so after finishing
> their current transaction?
This is in fact all dealt with for CREATE OR REPLACE FUNCTION, but
Jan's point holds also for CREATE OR REPLACE other-stuff. The syntax
change alone is the least of one's worries when implementing such
things.
We were foolish enough to accept a patch for CREATE OR REPLACE FUNCTION
that did not deal with propagating the changes, and had to do a lot of
work to clean up after it. We will not be so forgiving next time...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Castle | 2002-02-11 20:20:22 | Re: what's the meaning of the word "Tioga" in source |
Previous Message | Liam DeMasi | 2002-02-11 19:45:43 | having trouble with PostgreSQL 7.1.3 |
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2002-02-11 20:28:59 | Re: GiST on 64-bit box |
Previous Message | mlw | 2002-02-11 19:49:10 | Oracle compatibility |