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

pgsql: Further refine patch for commenting operator implementationfunc

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Further refine patch for commenting operator implementationfunc
Date: 2011-03-03 20:56:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
Further refine patch for commenting operator implementation functions.

Instead of manually maintaining the "implementation of XXX operator"
comments in pg_proc.h, delete all those entries and let initdb create
them via a join.  To let initdb figure out which name to use when there
is a conflict, change the comments for deprecated operators to say they
are deprecated --- which seems like a good thing to do anyway.



Modified Files
src/bin/initdb/initdb.c                  |   13 +
src/include/catalog/catversion.h         |    2 +-
src/include/catalog/pg_operator.h        |   51 ++-
src/include/catalog/pg_proc.h            |  704 +-----------------------------
src/test/regress/expected/opr_sanity.out |   35 +-
src/test/regress/sql/opr_sanity.sql      |   23 +-
6 files changed, 86 insertions(+), 742 deletions(-)

pgsql-committers by date

Next:From: Andrew DunstanDate: 2011-03-04 00:44:45
Subject: pgsql: Add a comment explaining the recent fix for plpython breakagein
Previous:From: Tom LaneDate: 2011-03-03 18:22:34
Subject: pgsql: Fix citext's upgrade-from-unpackaged script to set itscollation

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