From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Luiz Hugo Ronqui <lronqui(at)tce(dot)sp(dot)gov(dot)br>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump / pg_restore option |
Date: | 2020-07-08 19:34:58 |
Message-ID: | 0418b5a3-255a-a11c-bff3-1f48aa5878ab@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 7/8/20 12:27 PM, Luiz Hugo Ronqui wrote:
> Hello all!
>
> I’m experimenting with options to upgrade databases from older (v9.x) to
> more recent (probably v11) versions of PostgreSql and, partitioning some
> large tables during the process.
>
> The idea was:
>
> 1)To make a dump of the old database, wich I’ve done with the custom format
>
> 2)To restore the section “pre-data” on the new instalation
>
> 3)To make the desired changes, creating the partitions structures (quite
> simple: by ranges of “year” columns)
>
> 4)To restore the section “data”
>
> 5)To restore the section “post-data”
>
> It all went well until step 5, but the creation of FOREIGN KEYS on the
> partitioned tables raised errors, because of the “ALTER TABLE ONLY
> <name> ADD CONSTRAINT...” syntax of pg_dump output file.
>
> As it is needed that the partitions do exist in the previous step, that
> “ONLY” clause creates a situation that needs some more scripts to overcome.
>
> I’ve checked that the pg_dump v11 generates different versions of
> commands for partitioned and non-partitioned tables.
>
> Is there a parameter to suppress that keyword, or some other option I
> coud use?
Why not just restore the dump file as is and then partition the tables?
>
> Thanks in advance!
>
> Regards
>
> Luiz Hugo Ronqui
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-07-08 21:26:48 | Re: Is this a bug in pg_current_logfile() on Windows? |
Previous Message | Luiz Hugo Ronqui | 2020-07-08 19:27:47 | pg_dump / pg_restore option |