Thank you, Tom, for this valuable information.
On Tue, 01 Sep 2020 11:02:01 -0400
1Tom Lane wrote:
> visibility rules are the same as for any other function. So the
> answer to the OP's question depends on the transaction's isolation
> level and (for typical PLs) on whether the function is VOLA
Adrian Klaver writes:
> As I understand it a trigger function runs in its own transaction so the
> rules from below apply:
> https://www.postgresql.org/docs/12/transaction-iso.html
No, a trigger is part of the calling transaction. There's nothing special
about it other than the condition causin
On 9/1/20 7:07 AM, Dirk Lattermann wrote:
Hello!
Since unfortunately nobody has yet replied to my question, I'd like to
know if this is the right list to ask this question on or if I should
try another mailing list.
Maybe the answer is too obvious, but in that case I'd appreciate a
short hint to
Hello!
Since unfortunately nobody has yet replied to my question, I'd like to
know if this is the right list to ask this question on or if I should
try another mailing list.
Maybe the answer is too obvious, but in that case I'd appreciate a
short hint to help me finding it.
Maybe it's a hard quest
Hello,
I'd like to understand the visibility of data changes made by other
transactions when executing SQL commands in a trigger function in READ
COMMITTED isolation level.
I could not find this covered in the trigger documentation (which
already has some good sections about SQL command visibility
