From: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: sequences and pg_upgrade |
Date: | 2016-09-15 12:59:51 |
Message-ID: | b3f0c17e-744f-5d1a-84eb-c71a72a45902@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-09-15 13:35:30 | Re: palloc() too large on pg_buffercache with large shared_buffers |
Previous Message | Ashutosh Bapat | 2016-09-15 12:58:05 | Re: Declarative partitioning - another take |