hubert depesz lubaczewski <depesz@xxxxxxxxxx> writes: > On Sat, Jan 28, 2012 at 01:10:39PM -0500, Tom Lane wrote: >> Um, yes. Read the manual. >> http://www.postgresql.org/docs/9.1/static/extend-extensions.html#AEN51966 > Yes, but: > If you create table using extensions, and the you insert data to it > - this data will *not* be dumped using pg_dump. > If you mark the table with pg_extension_config_dump() - the data fro the > table will be dumped *always* - even for -s dump of another table. Yes, that's the intended behavior. The purpose of the configuration-table feature is to dump data that is needed for an extension to operate properly --- for instance postgis has some auxiliary tables that are best treated as part of the schema. If you think the contents of a table are not effectively schema information, then you shouldn't mark it as pg_extension_config_dump. > I have since made some tests, and it looks like the dumping thing is > fixed in 9.2devel from git HEAD, which seems to suggest that it will > work sanely in 9.1.3 - so the point is kind of moot. What tests were those exactly? I'm not aware of any agreed changes in this area. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
