Re: sequences and pg_upgrade - Mailing list pgsql-hackers

From Anastasia Lubennikova
Subject Re: sequences and pg_upgrade
Date
Msg-id b3f0c17e-744f-5d1a-84eb-c71a72a45902@postgrespro.ru
Whole thread Raw
In response to Re: sequences and pg_upgrade  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: sequences and pg_upgrade  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
15.09.2016 15:29, Peter Eisentraut:
> On 9/14/16 8:52 AM, Anastasia Lubennikova wrote:
>> Could you clarify, please, why do we dump sequence in schemaOnly mode?
>> +    if (dopt.schemaOnly && dopt.sequence_data)
>> +        getSequenceData(&dopt, tblinfo, numTables, dopt.oids);
> The point of this patch is that with the new option, you can dump
> sequence data (but not table data) alongside with the schema.  This
> would be used by pg_upgrade for the reasons described at the beginning
> of the thread.
>

Oh, thank you. Now I see.
Somewhy I thought that it *always* dumps sequence data in schemaOnly mode.
Which is definitely not true.

-- 
Anastasia Lubennikova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company




pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Declarative partitioning - another take
Next
From: Robert Haas
Date:
Subject: Re: palloc() too large on pg_buffercache with large shared_buffers