From: | "John Casey" <john(dot)casey(at)innovisors(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Loading Data Dumps for Tables Containing BDR Global Sequence |
Date: | 2015-01-03 16:14:41 |
Message-ID: | 002e01d02770$622ed080$268c7180$@innovisors.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
We have been trying to load our existing database that contains local
sequences into a BDR-based database with global sequences. So, we update our
schema in the new database to USING bdr for all sequences. We make certain
all tables have a primary key. Then we dump our data from our existing
database.
We dump our existing database, including schema. We update the existing
local sequences to USING bdr and remove the other initialization parameters.
Then we must remove all setval's that occur after the COPY statements;
because, BDR does not like them. We can load this data; but, the global
sequences are all initialized to 1 on our primary database and 15000 on our
DR database.
We have went so far as to write a program that selects the max(id) on each
table; then, it calls nextval until it reaches a value greater to or equal
the max(id). This has to be run on all BDR nodes. Needless to say, this is
slow and is a bad solution.
There just doesn't seem to be a good way to accomplish this operation, at
least not a documented way I have been able to find.
From | Date | Subject | |
---|---|---|---|
Next Message | John Casey | 2015-01-03 16:33:53 | ALTER TABLE to ADD BDR global sequence |
Previous Message | John Casey | 2015-01-03 15:52:09 | Re: bdr_init_copy fails when starting 2nd BDR node |