pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kris Kiger <kris@musicrebellion.com>
To: pgsql-admin@postgresql.org
Subject: Concurrency
Date: Mon, 09 May 2005 12:21:10 -0500
Message-ID: <427F9C06.3070206@musicrebellion.com> (raw)
In-Reply-To: <671060015.20031010095617@roaddep.ru>
References: <671060015.20031010095617@roaddep.ru>

Quick question.  I lock a table, call it table X, and then issue two 
updates on that table.  The two updates are left waiting.  I then unlock 
the table.   The two updates go through.  My question is, is there a 
predictable way to determine which query will be executed first?  Thanks 
in advance

Kris



view thread (5+ messages)  latest in thread

Message-ID: <427F9C06.3070206@musicrebellion.com>
Permalink:  ../427F9C06.3070206@musicrebellion.com/
Also on:    postgresql.org/message-id/427F9C06.3070206@musicrebellion.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: kris@musicrebellion.com
  Subject: Re: Concurrency
  In-Reply-To: <427F9C06.3070206@musicrebellion.com>
  References: <671060015.20031010095617@roaddep.ru> <427F9C06.3070206@musicrebellion.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox