| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Paragon Corporation <lr(at)pcorp(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org, Paul Ramsey <pramsey(at)opengeo(dot)org>, Mark Cave-Ayland <mark(dot)cave-ayland(at)ilande(dot)co(dot)uk>, strk <strk(at)keybit(dot)net>, Chris Hodgson <chodgson(at)refractions(dot)net> |
| Subject: | Re: BUG #6640: pg_dump does not always dump data of tables marked as editable in extension |
| Date: | 2012-05-22 20:06:21 |
| Message-ID: | CA+TgmobRRR4V50-CRnKDaxrGbJYcbgfHc2biFqXh1+2W91QO3Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, May 20, 2012 at 1:53 PM, Paragon Corporation <lr(at)pcorp(dot)us> wrote:
> Okay understood. We had planned to do something along this line of having a
> where condition for the extension or putting the custom spatial_ref_sys in 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 backup
> 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. Is that expected behavior that it doesn't?
Extensions are not schema objects.
But it seems like maybe we need a pg_dump --extension=XYZ option.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-05-22 20:08:13 | Re: BUG #6653: Service does not start in standby-mode |
| Previous Message | Robert Haas | 2012-05-22 20:03:07 | Re: BUG #6650: CPU system time utilization rising few times a day |