MIME-Version: 1.0
In-Reply-To: <571451BF.9070606@gmx.net>
References: <568C27BD.8030402@free.fr>
	<CAB7nPqS_v=s7L0jsx2bL1NYz8YocKQFcw4G2zZ_6e8H4NNpNUg@mail.gmail.com>
	<569E992B.20606@free.fr>
	<571451BF.9070606@gmx.net>
Date: Mon, 18 Apr 2016 13:33:02 +0900
Message-ID: 
 <CAB7nPqRpS_=N+epC67nCfE+C0dNr+dv-GNhu5xD6kByM9apqTg@mail.gmail.com>
Subject: Re: pg_extension_config_dump() function and sequences
From: Michael Paquier <michael.paquier@gmail.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Philippe BEAUDOIN <phb.emaj@free.fr>, pgsql-docs@postgresql.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

On Mon, Apr 18, 2016 at 12:17 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> On 01/19/2016 03:14 PM, Philippe BEAUDOIN wrote:
>> Le 18/01/2016 07:10, Michael Paquier a =C3=A9crit :
>>> On Wed, Jan 6, 2016 at 5:29 AM, Philippe BEAUDOIN <phb.emaj@free.fr>
>>> wrote:
>
>>>> 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.
>
> committed

Thanks. I completely forgot this patch..
--=20
Michael


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