Re: access to original-statement predicates in an INSTEAD-OF rowtrigger - Mailing list pgsql-general

From Adrian Klaver
Subject Re: access to original-statement predicates in an INSTEAD-OF rowtrigger
Date
Msg-id 6ea3b732-1f37-41c9-29a1-65f3aaebb6cd@aklaver.com
Whole thread Raw
In response to Re: access to original-statement predicates in an INSTEAD-OF rowtrigger  (John Lumby <johnlumby@hotmail.com>)
Responses Re: access to original-statement predicates in an INSTEAD-OF rowtrigger  (John Lumby <johnlumby@hotmail.com>)
List pgsql-general
On 11/15/19 1:54 PM, John Lumby wrote:
> Adrian Klaver wrote :
>> 
>> Seems you are looking for Serializable Isolation Level:
>> 
> 
> True ,   that would solve the race condition,  but it is too drastic.
> We need to run with Read Committed.
> 
> I am looking for a solution which does not alter the application or 
> overall behaviour,
> but just addresses detecting which predicates to apply in some way.

Not sure how that could be pulled off with Read Committed as it would 
involve predicting the future from the POV of the transaction.

> 
> Cheers,  John
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: John Lumby
Date:
Subject: Re: access to original-statement predicates in an INSTEAD-OF rowtrigger
Next
From: Palle Girgensohn
Date:
Subject: Re: here does postgres take its timezone information from?