From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Philippe BEAUDOIN <phb(dot)emaj(at)free(dot)fr>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: pg_extension_config_dump() function and sequences |
Date: | 2016-04-18 04:33:02 |
Message-ID: | CAB7nPqRpS_=N+epC67nCfE+C0dNr+dv-GNhu5xD6kByM9apqTg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Mon, Apr 18, 2016 at 12:17 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On 01/19/2016 03:14 PM, Philippe BEAUDOIN wrote:
>> Le 18/01/2016 07:10, Michael Paquier a écrit :
>>> On Wed, Jan 6, 2016 at 5:29 AM, Philippe BEAUDOIN <phb(dot)emaj(at)free(dot)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..
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Law | 2016-04-18 05:30:00 | Some minor error fixes |
Previous Message | Peter Eisentraut | 2016-04-18 03:17:19 | Re: pg_extension_config_dump() function and sequences |