Re: Does a the block of code within a stored procedure constitute - Mailing list pgsql-sql

From Rod Taylor
Subject Re: Does a the block of code within a stored procedure constitute
Date
Msg-id 1059698237.33557.8.camel@jester
Whole thread Raw
In response to Does a the block of code within a stored procedure constitute a transaction?  (<btober@seaworthysys.com>)
Responses Re: Does a the block of code within a stored procedure constitute a transaction?
List pgsql-sql
> What I need to know is whether or not this is multi-user safe, i.e., will
> the block of code in the procedure execute as a transaction so that if
> more than one clerk creates an expense report for the same employee
> simultaneously is it possible or impossible that value of the
> employee.expense_report_seq gets updated by the second clerk between the
> SELECT and UPDATE statements invoked by the first clerk?
>
> And as a follow-up, should I add the FOR UPDATE clause to the SELECT
> statement?

SELECT .. FOR UPDATE would be appropriate.

However, you could also do an update + 1 first and the select second to
find what you changed the value to.

pgsql-sql by date:

Previous
From: Andrew Gould
Date:
Subject: Re: [GENERAL] ALTER TABLE ... DROP CONSTRAINT
Next
From: Tom Lane
Date:
Subject: Re: join optimization problem