Re: access to original-statement predicates in an INSTEAD-OF row trigger

From: John Lumby <johnlumby(at)hotmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org>
Subject: Re: access to original-statement predicates in an INSTEAD-OF row trigger
Date: 2019-11-16 14:52:19
Message-ID: DM6PR06MB55625FC99325B3A33EE2EC8CA3730@DM6PR06MB5562.namprd06.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/15/19 17:38, Adrian Klaver wrote:
> On 11/15/19 1:54 PM, John Lumby wrote:
>> Adrian Klaver wrote :
>>>
>> 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.
>

No need for time-travel!
Let me re-phrase the question in a simpler fashion :
How can a row trigger access the original SQL statement at the root of
the current operation?
Either in string form or any other form (e.g. parse tree).

>>
>> Cheers, John
>>
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2019-11-16 15:35:58 Re: Function performance degrades after repeated execution
Previous Message Dave Roberge 2019-11-16 14:22:16 Function performance degrades after repeated execution