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

pgsql: Put back planner's ability to cache the results of

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Put back planner's ability to cache the results of
Date: 2007-01-22 20:00:40
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
Log Message:
Put back planner's ability to cache the results of mergejoinscansel(),
which I had removed in the first cut of the EquivalenceClass rewrite to
simplify that patch a little.  But it's still important --- in a four-way
join problem mergejoinscansel() was eating about 40% of the planning time
according to gprof.  Also, improve the EquivalenceClass code to re-use
join RestrictInfos rather than generating fresh ones for each join
considered.  This saves some memory space but more importantly improves
the effectiveness of caching planning info in RestrictInfos.

Modified Files:
        copyfuncs.c (r1.362 -> r1.363)
        outfuncs.c (r1.294 -> r1.295)
        costsize.c (r1.176 -> r1.177)
        equivclass.c (r1.1 -> r1.2)
        prepunion.c (r1.136 -> r1.137)
        restrictinfo.c (r1.52 -> r1.53)
        selfuncs.c (r1.220 -> r1.221)
        relation.h (r1.133 -> r1.134)
        selfuncs.h (r1.38 -> r1.39)

pgsql-committers by date

Next:From: Bruce MomjianDate: 2007-01-22 23:06:37
Subject: pgsql: Update my email address in FAQ.
Previous:From: Bruce MomjianDate: 2007-01-22 19:38:05
Subject: pgsql: Use errhint() for WIN32 SIGTERM message, where possible.

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