Re: Locking for function creation

Mark Morgan Lloyd wrote:
> If there's a risk that multiple clients will try to execute a 'create or replace
> function' simultaneously, what's the recommended practice for putting it in a
> transaction and/or locking it? If a lock's incolved what should this be applied
> to- the table that the function is most likely to be involved with, an arbitrary
> table, or a dummy table specifically reserved for this purpose?

What problem are you trying to prevent here? Do you want a particular
version of the function to be available for a certain amount of time?

--
   Richard Huxton
   Archonet Ltd