From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | phb(dot)emaj(at)free(dot)fr |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6682: pg_dump and sequence values of serial columns for extension configuration tables |
Date: | 2012-06-09 22:20:18 |
Message-ID: | 5379.1339280418@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
phb(dot)emaj(at)free(dot)fr writes:
> When a table is registered as an extension configuration table and contains
> a serial column, the current value of the sequence associated to this serial
> column is not dumped by pg_dump.
I think the way to make that happen is to also register the sequence as
a configuration table of the extension. It's not clear to me that that
should happen by default; it would depend a lot on how the extension
designer intends to manage modifications of the table.
> echo "--> And sequences cannot be registered as 'content to be dumped'"
> $PGBIN/psql -ac "select
> pg_catalog.pg_extension_config_dump('tbl1_col1_seq','');"
This test proves nothing of the kind. Please read the error message:
ERROR: pg_extension_config_dump() can only be called from an SQL script executed by CREATE EXTENSION
You have to do it in the extension's script.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2012-06-09 22:21:14 | Re: [BUGS] BUG #6680: error para ingresar |
Previous Message | Tom Lane | 2012-06-09 22:14:02 | Re: BUG #6683: dropping a table with a serial column from an extension needs to explicitely drop the associated seq |