Re: BUG #6640: pg_dump does not always dump data of tables marked as editable in extension

On Sun, May 20, 2012 at 1:53 PM, Paragon Corporation <lr@pcorp.us> wrote:
> Okay understood. =A0We had planned to do something along this line of hav=
ing a
> where condition for the extension or putting the custom spatial_ref_sys i=
n a
> separate table but hand't decided which way to go. So that will take care=
 of
> the handling custom records issue.
>
> So I guess the more major issue is a won't fix on both sides since a user
> will not be able to backup custom records without backing up the whole
> database. I don't see any option in 9.1 or 9.2 pg_dump to explicitly back=
up
> an extension and even backing up the schema an extension is installed in
> doesn't seem to do the trick.
>
> I would have expected backing up the schema an extension is installed in
> would backup the extension. =A0Is that expected behavior that it doesn't?

Extensions are not schema objects.

But it seems like maybe we need a pg_dump --extension=3DXYZ option.

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company