Re: BUG #6682: pg_dump and sequence values of serial columns for extension configuration tables

From: Philippe BEAUDOIN <phb(dot)emaj(at)free(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6682: pg_dump and sequence values of serial columns for extension configuration tables
Date: 2016-01-05 19:37:30
Message-ID: 568C1B7A.4070902@free.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Tom,

Here is a final answer to this very old thread, for the record.
You were right (as usual ;-)). It's indeed possible to register a
sequence as a "configuration table" using the pg_extension_config_dump()
function.

>> 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
>
>
May be a sentence about this in the documentation would be useful. I
will try to propose something.

Best regards. Philippe Beaudoin.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message skinneda 2016-01-05 22:22:15 BUG #13849: Need a parameter added similar to "edb_stmt_level_tx"
Previous Message maxk 2016-01-05 19:32:17 BUG #13848: 2016 Week Number Error