| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: NOWAIT doesn't work |
| Date: | 2012-10-31 14:07:42 |
| Message-ID: | CAFj8pRDhLZoxoBGq2So+VksVnhjbfYJrFyV9R7u_hrp5=UQ2SA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2012/10/31 Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>:
> Alvaro Herrera escribió:
>
>> Now, is this the right behavior? I'm not sure. But I know for certain
>> that making it behave as you expect is very tricky. The table lock is
>> grabbed during parse analysis; we'd have to postpone grabbing the lock
>> until after we have had the chance to notice that there's a FOR UPDATE
>> clause for the table with a NOWAIT option attached.
>
> Furthermore you could do it manually: just do a LOCK TABLE NOWAIT in the
> second session before the SELECT FOR UPDATE.
I understand now, thank you to all for information
Regards
Pavel
>
> --
> Álvaro Herrera http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-10-31 14:09:52 | pgsql: Fix erroneous choices of segNo variables |
| Previous Message | Alvaro Herrera | 2012-10-31 14:03:09 | Re: NOWAIT doesn't work |