From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Ernst-Georg Schmid <ernst(dot)georg(dot)schmid(at)googlemail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: How to inspect tuples during execution of a plan? |
Date: | 2016-10-13 20:36:17 |
Message-ID: | 3c27dc2f-dfe7-4c57-d891-9630b18f1507@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/12/16 2:58 AM, Ernst-Georg Schmid wrote:
>> Either of those would do, if you want to write change the executor.
>> >
> I used the ExeceutorRun_hook and it seems to work. The drawback is,
> that I have to provide my own implementation of ExecutePlan() which
> could make it incompatible over versions of PostgreSQL. I don't know
> how stable that function is over time.
There might be another possibility, which would be to use one of the
earlier hooks to change the query destination, and to implement a custom
receiver.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2016-10-13 21:07:46 | emergency outage requiring database restart |
Previous Message | Tom Lane | 2016-10-13 20:35:09 | Re: Conflicting constraint being merged |