On Mon, Jan 14, 2013 at 9:38 PM, Vlad Arkhipov <arhipov(at)dc(dot)baikal(dot)ru> wrote:
>>> Is there any simple way of getting a query for which a trigger was
>>> debug_query_string and ActivePortal->sourceText return the top query when
>>> there are nested triggers.
>> I believe - only if the trigger is written in C.
> Yes, the trigger is written in C. But I didn't find any way to get access to
> the current EState or QueryDesc from a trigger function. The only common
> place of a trigger and the corresponding EState/QueryDesc structs seems to
> be CurrentMemoryContext in a trigger function, which ancestor has to be (?)
> EState->es_query_cxt. It's an ugly solution of course.
Ah, I see. Yeah, I don't know of a good way to do that, although
there may be one.
> P.S. Is it a mistype EState->es_query_cxt? Should it be es_query_ctx?
I don't see why either of those is particularly better than the other.
"context" has a t both before and after the x.
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2013-01-15 20:02:23|
|Subject: Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)|
|Previous:||From: Stephen Frost||Date: 2013-01-15 19:53:29|
|Subject: Re: [PATCH] COPY .. COMPRESSED|