On Tue, May 31, 2011 at 8:43 PM, Cédric Villemain <cedric.villemain.deb...@gmail.com> wrote: > Yes, while here I noticed that the query was long to be killed. > I added a CHECK_FOR_INTERRUPT() in the for(;;) loop in nodeHashjoin.c. > It fixes the delay when trying to kill but I don't know about > performance impact this can have in this place of the code.
Well, seems easy enough to find out: just test the query with and without your patch (and without casserts). If there's no measurable difference on this query, there probably won't be one anywhere. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
