Re: sequences and pg_upgrade - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: sequences and pg_upgrade
Date
Msg-id b7887a5e-28f9-9d5e-4a22-a54728cbb771@2ndquadrant.com
Whole thread Raw
In response to Re: sequences and pg_upgrade  (Anastasia Lubennikova <a.lubennikova@postgrespro.ru>)
Responses Re: sequences and pg_upgrade  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On 9/30/16 12:50 PM, Anastasia Lubennikova wrote:
> The patches are good, no complaints.
> But again, I have the same question.
> I was confused, why do we always dump sequence data,
> because I'd overlooked the --sequence-data key. I'd rather leave this
> option,
> because it's quite non intuitive behaviour...
>   /* dump sequence data even in schema-only mode */

Here are rebased patches.

Regarding your question:  The initial patch had a separate option for
this behavior, which was then used by pg_upgrade.  It was commented that
this option is not useful outside of pg_upgrade, so it doesn't need to
be exposed as a user-facing option.  I agreed with that and removed the
option.  We can always add the option back easily if someone really
wants it, but so far no use case has been presented.  So I suggest we
proceed with this proposal ignoring whether this option is exposed or not.

--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: WAL consistency check facility
Next
From: Robert Haas
Date:
Subject: Re: Partition-wise join for join between (declaratively) partitioned tables