pgsql-server/src backend/commands/analyze.c ba ...

CVSROOT:    /cvsroot
Module name:    pgsql-server
Changes by:    tgl@svr1.postgresql.org    03/08/17 16:58:06

Modified files:
    src/backend/commands: analyze.c indexcmds.c opclasscmds.c
    src/backend/nodes: copyfuncs.c equalfuncs.c
    src/backend/optimizer/plan: createplan.c planner.c
    src/backend/parser: gram.y parse_clause.c parse_oper.c
    src/backend/utils/adt: acl.c arrayfuncs.c cash.c nabstime.c
                           ri_triggers.c ruleutils.c
    src/backend/utils/cache: Makefile lsyscache.c
    src/backend/utils/sort: tuplesort.c
    src/include/catalog: catversion.h pg_amop.h pg_amproc.h
                         pg_opclass.h pg_operator.h pg_proc.h
    src/include/nodes: nodes.h parsenodes.h
    src/include/parser: parse_clause.h parse_oper.h
    src/include/utils: acl.h builtins.h cash.h lsyscache.h
    src/test/regress/expected: circle.out geometry.out
                               geometry_1.out
    src/test/regress/sql: circle.sql geometry.sql
Added files:
    src/backend/utils/cache: typcache.c
    src/include/utils: typcache.h

Log message:
    Create a 'type cache'  that keeps track of the data needed for any particular
    datatype by array_eq and array_cmp; use this to solve problems with memory
    leaks in array indexing support.  The parser's equality_oper and ordering_oper
    routines also use the cache.  Change the operator search algorithms to look
    for appropriate btree or hash index opclasses, instead of assuming operators
    named '<' or '=' have the right semantics.  (ORDER BY ASC/DESC now also look
    at opclasses, instead of assuming '<' and '>' are the right things.)  Add
    several more index opclasses so that there is no regression in functionality
    for base datatypes.  initdb forced due to catalog additions.