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

Поиск
Список
Период
Сортировка
От John Lumby
Тема Re: access to original-statement predicates in an INSTEAD-OF rowtrigger
Дата
Msg-id DM6PR06MB55625FC99325B3A33EE2EC8CA3730@DM6PR06MB5562.namprd06.prod.outlook.com
обсуждение исходный текст
Ответ на Re: access to original-statement predicates in an INSTEAD-OF rowtrigger  (Adrian Klaver <adrian.klaver@aklaver.com>)
Ответы Re: access to original-statement predicates in an INSTEAD-OF row trigger
Список 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
>>
>
>




В списке pgsql-general по дате отправления:

Предыдущее
От: Dave Roberge
Дата:
Сообщение: Function performance degrades after repeated execution
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: Function performance degrades after repeated execution