Re: Extensions not dumped when --schema is used
Guillaume Lelarge <guillaume@lelarge.info>
From: Guillaume Lelarge <guillaume@lelarge.info>
To: Asif Rehman <asifr.rehman@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-02-03T17:42:11Z
Lists: pgsql-hackers
Hi, Thanks for the review. Le mer. 3 févr. 2021 à 18:33, Asif Rehman <asifr.rehman@gmail.com> a écrit : > The following review has been posted through the commitfest application: > make installcheck-world: tested, passed > Implements feature: tested, passed > Spec compliant: not tested > Documentation: not tested > > The patch applies cleanly and looks fine to me. However consider this > scenario. > > - CREATE SCHEMA foo; > - CREATE EXTENSION file_fdw WITH SCHEMA foo; > - pg_dump --file=/tmp/test.sql --exclude-schema=foo postgres > > This will still include the extension 'file_fdw' in the backup script. > Shouldn't it be excluded as well? > > The new status of this patch is: Waiting on Author > This behaviour is already there without my patch, and I think it's a valid behaviour. An extension doesn't belong to a schema. Its objects do, but the extension doesn't. -- Guillaume.
Commits
-
Tweak behavior of pg_dump --extension with configuration tables
- 344487e2db03 14.0 landed
-
Remove duplicated --no-sync switches in new tests of test_pg_dump
- 885a87641930 14.0 landed
-
Add support for --extension in pg_dump
- 6568cef26e0f 14.0 landed