Postgres Pro
Downloads
Home   >   mailing lists

Re: Actual row order in UPDATE and SELECT FOR UPDATE - Mailing list pgsql-general

From David G. Johnston
Subject Re: Actual row order in UPDATE and SELECT FOR UPDATE
Date
Msg-id CAKFQuwZktqAJt7sjYS170ZociDB+UKbU3hdU17EP+N5PCGBdPg@mail.gmail.com
Whole thread Raw
In response to Actual row order in UPDATE and SELECT FOR UPDATE  (Nikolai Zhubr <n-a-zhubr@yandex.ru>)
List pgsql-general
Tree view
On Mon, Feb 15, 2016 at 3:17 PM, Nikolai Zhubr <n-a-zhubr@yandex.ru> wrote:
Hello all,

I can't find any clear description of how to reliably figure and/or enforce specific row (locking) order within UPDATE and SELECT FOR UPDATE statements dealing with multiple rows.

​SQL is a set-oriented language.  Sets do not have order.  Therefore I don't understand your goal.  That said subqueries and ORDER BY may be solution.

David J.
​
 

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Actual row order in UPDATE and SELECT FOR UPDATE
Next
From: Vitaly Burovoy
Date:
Subject: Re: Actual row order in UPDATE and SELECT FOR UPDATE