Unanswered: Table locking and transaction isolation level
I am currently writing a procedure which will first update a row in a table and run a "select" statement against the table. The "select" statement will extract the row and thereafter display some values. The value will be unique per transaction
If I have multiple transactions executing the procedure and I want each individual transaction to display a new unique value, should I look at setting the transaction to serializable in the procedure and maybe consider table row locking?
It sounds like you are trying to implement your own sequence logic. If that is the case, then don't do this. Use a sequence to generate unique values. Everything that you can possibly write is either not scalable or not correct (in a multi-user environment).
Cheers for the response. I forgot about using RETURNING and will look at implementing that.
We have looked at using Sequences however we use various lookup tables for an application. I have seen a few articles about Sequences missing a value and that is a risk which we can't afford to take.