Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4P7uRA69155 for ; Fri, 25 May 2001 03:56:28 -0400 (EDT) (envelope-from ler@lerctr.org) Received: (from ler@localhost) by lerami.lerctr.org (8.12.0.Beta7/8.12.0.Beta7/20010318/$Revision: 1.22 $) id f4P7uN5B026539 for pgsql-sql@postgresql.org; Fri, 25 May 2001 02:56:23 -0500 (CDT) (envelope-from ler) Date: Fri, 25 May 2001 02:56:23 -0500 From: Larry Rosenman To: PostgreSQL SQL List Subject: locking/concurrency question. Message-ID: <20010525025623.A26048@lerami.lerctr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.18i X-Mailer: Mutt http://www.mutt.org/ X-Archive-Number: 200105/269 X-Sequence-Number: 3097 I have an app that does essentially the following query: SELECT host(netblock),masklen(netblock),netblock,netmask(netblock) FROM networks WHERE status=get_status_code('available') AND parent_asn=4278 AND masklen(netblock)=xx -- where xx is a legit mask size FOR UPDATE LIMIT 1; inside a BEGIN TRANSACTION block. My question is: if a 2nd copy of this query runs with the same size, will it skip the locked row, or wait for commit? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749