| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Extensions not dumped when --schema is used |
| Date: | 2020-05-20 09:55:24 |
| Message-ID: | CAA722E2-218F-46F8-BE3A-2D7B4CB6A877@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 20 May 2020, at 11:38, Guillaume Lelarge <guillaume(at)lelarge(dot)info> wrote:
> Actually, "dump all extensions" (#3) would make sense to me, and has my vote.
Wouldn't that open for another set of problems when running with --schema=bar
and getting errors on restoring for relocatable extensions like these:
CREATE EXTENSION IF NOT EXISTS pg_trgm WITH SCHEMA foo;
Only dumping extensions depended on has the same problem of course.
> People dump databases, schemas, and tables. Theu usually don't know which extensions those objects depend on.
That I totally agree with, question is how we best can help users here.
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2020-05-20 10:01:23 | Re: pgindent vs dtrace on macos |
| Previous Message | Peter Eisentraut | 2020-05-20 09:52:25 | pgindent vs dtrace on macos |