Le Lundi 11 Février 2002 20:35, Jan Wieck a écrit :
> 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?
>
> The reason for this feature not beeing implemented yet is not
> "that just noone is in the mood for". It is that the general
> multiuser support structures aren't in place and a little
> local sandbox-hack just wouldn't cut it.
Thank you for the explaination. I feel stupid. Please, don't flame me for
this now :
Could PostgreSQL be working in two modes : development (SET DEVELOPMENT MODE)
and production (SET PRODUCTION MODE).
1) In development mode, each object has an md5 signature showing whether the
object is updated or not. If the object has changed, it is reloaded. This
would work even in a cluster. Object modification and deletion would only be
allowed in development mode.
2) In production, object deletion and modification would not be possible. No
need for md5 signatures then.
Switching from production <-> development would only be possible after all
transactions have ended. Pretty stupid, I agree, but this would make life
easier. Just my 0,00002 cents.
Cheers,
Jean-Michel
