pgsql: Redefine create_upper_paths_hook as being invoked once per upper - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Redefine create_upper_paths_hook as being invoked once per upper
Date
Msg-id E1aq3uF-0004D5-FA@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Redefine create_upper_paths_hook as being invoked once per upper relation.

Per discussion, this gives potential users of the hook more flexibility,
because they can build custom Paths that implement only one stage of
upper processing atop core-provided Paths for earlier stages.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/f1f01de145d0aaca80e6cf8b2ccb7e7f4ed1ad02

Modified Files
--------------
src/backend/optimizer/plan/planner.c   | 45 ++++++++++++++++++++++++++--------
src/backend/optimizer/prep/prepunion.c |  7 +++++-
src/include/optimizer/planner.h        |  6 +++--
3 files changed, 45 insertions(+), 13 deletions(-)


pgsql-committers by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: [HACKERS] Re: pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] Re: pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <