Tom, 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? Thanks, Regina > -----Original Message----- > From: Tom Lane [mailto:t...@sss.pgh.pa.us] > Sent: Sunday, May 20, 2012 1:28 PM > To: l...@pcorp.us > Cc: pgsql-bugs@postgresql.org > Subject: Re: [BUGS] BUG #6640: pg_dump does not always dump > data of tables marked as editable in extension > > l...@pcorp.us writes: > > This seems to be only an issue if a user individually chooses to > > backup a table marked as editable in an extension, but > works fine if > > full backup is chosen. > > AFAICT this is a misunderstanding of the intended behavior of > extension configuration tables. The data in them will be > dumped when, and only when, the extension itself is included > in the dump. Moreover, if you have a mixture of > extension-provided and user-provided data in the table, as > seems to be the case here, you really need to take measures > to keep those separate so that you can dump only the > user-provided entries. > This is not a "fire and forget" type of feature, it requires > nontrivial effort on the part of the extension author to make > it useful. Please see > http://www.postgresql.org/docs/9.1/static/extend-extensions.ht ml#AEN51978 > > regards, tom lane > -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
