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. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
