Re: Extensions not dumped when --schema is used

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Extensions not dumped when --schema is used
Date: 2021-02-20 21:39:24
Message-ID: CAECtzeXRygssgyWkqTtkc1jBrrMtB8WsrS_fOUmfPq7QyjO1+g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le sam. 20 févr. 2021 à 17:31, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> a écrit :

> Michael Paquier <michael(at)paquier(dot)xyz> writes:
> > As presented in this patch, specifying both --extension and
> > --table/--schema means that pg_dump will dump both tables and
> > extensions matching the pattern passed down. But shouldn't extensions
> > not be dumped if --table or --schema is used? Combining --schema with
> > --table implies that the schema part is ignored, for instance.
>
> I haven't read the patch, but the behavior I would expect is:
>
> 1. If --extension=pattern is given, then extensions matching the
> pattern are included in the dump, regardless of other switches.
> (Conversely, use of --extension doesn't affect choices about what
> other objects are dumped.)
>
> 2. Without --extension, the behavior is backward compatible,
> ie, dump extensions in an include_everything dump but not
> otherwise.
>
>
Yes, that's what it's supposed to do.

Maybe we could have a separate discussion as to which switches turn
> off include_everything, but that seems independent of this patch.
>
>
+1

--
Guillaume.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-02-20 22:20:19 Bizarre behavior of \w in a regular expression bracket construct
Previous Message Guillaume Lelarge 2021-02-20 21:38:36 Re: Extensions not dumped when --schema is used