From: | Mark Morgan Lloyd <markMLl(dot)pgsql-general(at)telemetry(dot)co(dot)uk> |
---|---|
To: | pgsql-general(at)PostgreSQL(dot)org |
Subject: | Re: Locking for function creation |
Date: | 2006-12-04 15:38:58 |
Message-ID: | 45744112.96361B5B@telemetry.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Richard Huxton wrote:
>
> Mark Morgan Lloyd wrote:
> >
> > If I might ask a related question- assuming that a client has grabbed a
> > restrictive lock during a transaction that e.g. is create/replacing functions,
> > what happens to other sessions that attempt to run a select or update- will they
> > fail (i.e. an implicit NOWAIT) or will they wait until the lock is released?
> > Does this vary depending on whether a select/update is within an explicit
> > transaction?
>
> They will wait without an explicit NOWAIT. This applies whether the
> transaction is explicit or implicit.
Just what I was hoping. Many thanks for your help :-)
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2006-12-04 15:45:07 | Re: pgsql bug found? |
Previous Message | Richard Huxton | 2006-12-04 15:29:42 | Re: Locking for function creation |