From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Extensions not dumped when --schema is used |
Date: | 2020-05-20 08:06:01 |
Message-ID: | CAECtzeXOt4cnMU5+XMZzxBPJ_wu76pNy6HZKPRBL-j7yj1E4+g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
I've discovered something today that I didn't really expect. When a user
dumps a database with the --schema flag of pg_dump, extensions in this
schema aren't dumped. As far as I can tell, the documentation isn't clear
about this ("Dump only schemas matching pattern; this selects both the
schema itself, and all its contained objects."), though the source code
definitely is ("We dump all user-added extensions by default, or none of
them if include_everything is false (i.e., a --schema or --table switch was
given).", in pg_dump.c).
I was wondering the reason behind this choice. If anyone knows, I'd be
happy to hear about it.
I see two things:
* it's been overlooked, and we should dump all the extensions available in
a schema if this schema has been selected through the --schema flag.
* it's kind of like the large objects handling, and I'd pretty interested
in adding a --extensions (as the same way there is a --blobs flag).
Thanks.
Regards.
--
Guillaume.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2020-05-20 08:06:55 | Re: explicit_bzero for sslpassword |
Previous Message | Peter Eisentraut | 2020-05-20 08:05:29 | Re: Expand the use of check_canonical_path() for more GUCs |