From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Keith Fiske <keith(at)omniti(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Extension table data |
Date: | 2012-06-09 03:38:41 |
Message-ID: | 21083.1339213121@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Keith Fiske <keith(at)omniti(dot)com> writes:
> I've read the documentation for extensions and how their data is not
> normally dumped by pg_dump and how to configure the table so it should
> dump its data
> http://www.postgresql.org/docs/9.1/static/extend-extensions.html
> However, after setting this option for the tables, the data is not
> being dumped when I do a pg_dump of either individual tables or the
> schema I've installed the extension to.
IIRC, the design intention is that such a table's data would be dumped
when (and only when) the extension is dumped. That is, I'd expect to
see a "CREATE EXTENSION foo;" and then data for the extension's tables.
The partial-dump scenarios you mention wouldn't dump extensions, hence
not extension table data either.
Whether this design is a good one is still under debate, but I think
pg_dump is operating as designed here ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Keith Fiske | 2012-06-09 06:56:15 | Re: Extension table data |
Previous Message | Thomas Munro | 2012-06-08 21:27:52 | ctid ranges |