| From: | nickbarnes01(at)gmail(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #13581: pg_dump omits extension versions |
| Date: | 2015-08-20 12:22:33 |
| Message-ID: | 20150820122233.7668.46092@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 13581
Logged by: Nick Barnes
Email address: nickbarnes01(at)gmail(dot)com
PostgreSQL version: 9.4.4
Operating system: CentOS 6.6
Description:
pg_dump does not include a VERSION clause in CREATE EXTENSION statements. As
a result, the restored database will receive the default extension version
on the target cluster.
This can cause the restore to fail, if for example the structure of the
extension's configuration tables has changed, or the database has
dependencies on a dropped function, type, etc.
I realise that the VERSION clause can't be emitted by default, since old
versions of contrib extensions are not installable. Would an
--include-extension-version=<name> option be feasible?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-08-20 13:51:41 | Re: BUG #13581: pg_dump omits extension versions |
| Previous Message | martipamies | 2015-08-20 09:49:56 | BUG #13580: Fix namespace handling in xpath function, current functions collision |