Re: Queries getting older values (autocommit enabled) - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: Queries getting older values (autocommit enabled)
Date
Msg-id CAKFQuwbigrLcg5dGD6VUYGa+U-46q7xUgCbbMdPPWJBc3mki1Q@mail.gmail.com
Whole thread Raw
In response to Queries getting older values (autocommit enabled)  (Eudald Valcàrcel Lacasa <eudald.valcarcel@gmail.com>)
List pgsql-bugs
On Fri, Apr 24, 2020 at 9:04 AM Eudald Valcàrcel Lacasa <eudald.valcarcel@gmail.com> wrote:
Hello all,
I'm facing what seems like a bug and I've reached a dead end without finding a solution.

I'm executing a script that work on a postgresql table. This script is executed more than once at a time.
The table contains a column called status.
One of the scripts is checking the value on the column status and, if it's different than 1, it should do nothing. If it's 1 it changes its value to the new status (new value can be 1,2,3)


Read "The Locking Clause" in the SELECT command's documentation page and see if that helps.


David J.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16386: drop contraint in inherited table is missing in pg_dump backup
Next
From: PG Bug reporting form
Date:
Subject: BUG #16387: postgres12-* packages not in yum repo