From: | Cedar Cox <cedarc(at)visionforisrael(dot)com> |
---|---|
To: | Loïc Bourgeois <loic(dot)bourgeois(at)mobileway(dot)com> |
Cc: | pgsql-sql <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: please help |
Date: | 2001-04-08 22:55:37 |
Message-ID: | Pine.LNX.4.21.0104090155170.7109-100000@nanu.visionforisrael.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
It would be somewhat (very) useful to have something like this. We were
toying with the idea of making some sort of system to figure out if a
table is locked or not. In the end we decided to go with executing this
asynchronously and after a given timeout ask the user if they would like
to wait or cancel the request. Something like this may or may not work
for you..
-Cedar
On Fri, 6 Apr 2001, Loïc Bourgeois wrote:
> Yes but the option NOWAIT say to the instruction SELECT ... FOR UPDATE
> to not wait the unlock but to return the information the lines can't be
> lock.
> (Must retry late).
>
>
> Peter Eisentraut wrote:
>
> > Loïc Bourgeois writes:
> >
> >> What is the equivalent of the oracle request: SELECT ... FOR UPDATE
> >> NOWAIT, under PostGreSQL
> >
> >
> > I don't know Oracle, but there doesn't seem to be such a command in
> > PostgreSQL. If the table is already locked, the SELECT FOR UPDATE has to
> > wait.
> >
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Cedar Cox | 2001-04-08 23:03:21 | Re: Double-nesting quotes? |
Previous Message | Peter Eisentraut | 2001-04-08 21:15:57 | Re: open and closed paths ... |