| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | lr(at)pcorp(dot)us |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6640: pg_dump does not always dump data of tables marked as editable in extension |
| Date: | 2012-05-20 17:27:48 |
| Message-ID: | 5301.1337534868@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
lr(at)pcorp(dot)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.html#AEN51978
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paragon Corporation | 2012-05-20 17:53:25 | Re: BUG #6640: pg_dump does not always dump data of tables marked as editable in extension |
| Previous Message | Tom Lane | 2012-05-20 16:16:31 | Re: BUG #6651: macaddr length constraint violates standard |