Skip site navigation (1) Skip section navigation (2)

Re: Command Triggers, patch v11

From: "anarazel(at)anarazel(dot)de" <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org,Thom Brown <thom(at)linux(dot)com>,Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>
Subject: Re: Command Triggers, patch v11
Date: 2012-02-28 00:29:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> schrieb:

>Andres Freund <andres(at)anarazel(dot)de> writes:
>> I refreshed the patch so it works again on current HEAD. Basically
>> trivial fixes and dfd26f9c5f371437f243249025863ea9911aacaa. The
>latter doesn't 
>> seem necessary to me after the changes, so I simply ditched it. Am I
>> something?
>No, that was only needed because execMain.c was overriding somebody
>else's tuple receiver.  If you're putting the right receiver into the
>QueryDesc to start with, it shouldn't be necessary.
>I'm confused by this though:
>> This basically includes a revert of
>I don't find that commit ID anywhere.
That should have been the aforementioned commit. Must have screwed up the copy&paste buffer. Sorry for that.


Please excuse the brevity and formatting - I am writing this on my mobile phone.

In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2012-02-28 02:12:08
Subject: Re: Command Triggers
Previous:From: Noah MischDate: 2012-02-28 00:28:14
Subject: Re: foreign key locks, 2nd attempt

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group