pgsql: Fix old pg_dump oversight: default values for domains really need

Поиск
Список
Период
Сортировка
От tgl@postgresql.org (Tom Lane)
Тема pgsql: Fix old pg_dump oversight: default values for domains really need
Дата
Msg-id 20060221180143.697909DCA1C@postgresql.org
обсуждение исходный текст
Список pgsql-committers
Log Message:
-----------
Fix old pg_dump oversight: default values for domains really need to be dumped
by decompiling the typdefaultbin expression, not just printing the typdefault
text which may be out-of-date or assume the wrong schema search path.  (It's
the same hazard as for adbin vs adsrc in column defaults.)  The catalogs.sgml
spec for pg_type implies that the correct procedure is to look to
typdefaultbin first and consider typdefault only if typdefaultbin is NULL.
I made dumping of both domains and base types do that, even though in the
current backend code typdefaultbin is always correct for domains and
typdefault for base types --- might as well try to future-proof it a little.
Per bug report from Alexander Galler.

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
    pgsql/src/bin/pg_dump:
        pg_dump.c (r1.422.2.2 -> r1.422.2.3)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c.diff?r1=1.422.2.2&r2=1.422.2.3)

В списке pgsql-committers по дате отправления:

Предыдущее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Fix old pg_dump oversight: default values for domains really need
Следующее
От: neilc@postgresql.org (Neil Conway)
Дата:
Сообщение: pgsql: Cleanup the usage of ScanDirection: use the symbolic names for