Fix pg_dump's handling of extension-member casts and languages.

pg_dump has some heuristic rules for whether to dump casts and procedural
languages, since it's not all that easy to distinguish built-in ones from
user-defined ones.  However, we should not apply those rules to objects
that belong to an extension, but just use the perfectly well-defined rules
for what to do with extension member objects.  Otherwise we might
mistakenly lose extension member objects during a binary upgrade (which is
the only time that we'd want to dump extension members).

Branch
------
master

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

Modified Files
--------------
src/bin/pg_dump/pg_dump.c |   87 +++++++++++++++++++++++++++------------------
1 files changed, 52 insertions(+), 35 deletions(-)

pgsql-committers by date

Next:	From: Bruce Momjian	Date: 2011-05-18 16:14:06
	Subject: pgsql: Fix pg_upgrade build problem on Windows when using X_OK access
Previous:	From: Bruce Momjian	Date: 2011-05-16 16:33:09
	Subject: pgsql: Update pg_upgrade directory check error message.