pgsql: Add ALTER EXTENSION ADD/DROP ACCESS METHOD, and use it in pg_upg

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Add ALTER EXTENSION ADD/DROP ACCESS METHOD, and use it in pg_upg
Date: 2016-10-02 18:31:33
Message-ID: E1bqlXx-0003LD-Ts@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Add ALTER EXTENSION ADD/DROP ACCESS METHOD, and use it in pg_upgrade.

Without this, an extension containing an access method is not properly
dumped/restored during pg_upgrade --- the AM ends up not being a member
of the extension after upgrading.

Another oversight in commit 473b93287, reported by Andrew Dunstan.

Report: <f7ac29f3-515c-2a44-21c5-ec925053265f(at)dunslane(dot)net>

Branch
------
REL9_6_STABLE

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

Modified Files
--------------
doc/src/sgml/ref/alter_extension.sgml | 1 +
src/backend/parser/gram.y | 11 ++++++++++-
src/bin/pg_dump/pg_dump.c | 3 +++
3 files changed, 14 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2016-10-03 00:36:39 Re: [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.
Previous Message Tom Lane 2016-10-02 16:33:54 pgsql: Avoid leaking FDs after an fsync failure.