Subject: Re: pg_extension_config_dump() function and sequences
To: Michael Paquier <michael.paquier@gmail.com>
References: <568C27BD.8030402@free.fr>
 <CAB7nPqS_v=s7L0jsx2bL1NYz8YocKQFcw4G2zZ_6e8H4NNpNUg@mail.gmail.com>
Cc: pgsql-docs@postgresql.org
From: Philippe BEAUDOIN <phb.emaj@free.fr>
Message-ID: <569E992B.20606@free.fr>
Date: Tue, 19 Jan 2016 21:14:35 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: 
 <CAB7nPqS_v=s7L0jsx2bL1NYz8YocKQFcw4G2zZ_6e8H4NNpNUg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

Le 18/01/2016 07:10, Michael Paquier a écrit :
> On Wed, Jan 6, 2016 at 5:29 AM, Philippe BEAUDOIN <phb.emaj@free.fr> wrote:
>> The page "Packaging Related Objects into an Extension" has a third chapter
>> dealing with "Extension Configuration Tables". A final paragraph would be
>> useful to explain that:
>>
>> The pg_extension_config_dump() function can also register sequences, so that
>> the current properties of the registered sequences are saved by pg_dump and
>> later restored. The function can support sequences either explicitely
>> created with an ALTER SEQUENCE statement or implicitely created when a table
>> contains SERIAL or BIGSERIAL columns. Note that the sequences associated to
>> SERIAL or BIGSERIAL columns of a configuration table need to be registered
>> using the pg_extension_config_dump() function if one wants to restore the
>> properties they had at pg_dump time.
> Instead of a single paragraph, perhaps we could make things more
> generic like in the attached?
It looks much better, indeed.

Philippe.


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs