I figured out what happened here. Total user error. Got a little too excited by the new ability to add tables/sequences by regex and just used '.*' for the sequences.
Guess what got added:
3 | 253138138 | sl_action_seq | _migration | 1 |
replicated sequence
4 | 253138136 | sl_event_seq | _migration | 1 |
replicated sequence
5 | 253138134 | sl_local_node_id | _migration | 1 |
replicated sequence
6 | 253138140 | sl_log_status | _migration | 1 |
replicated sequence
7 | 253137956 | sl_nodelock_nl_conncnt_seq | _migration | 1 |
replicated sequence
So, setting sl_local_node_id to the correct value gets it going again, but of
course I had a ton of pkey conflicts in sl_event.
I guess I'd better resync this thing.
On Feb 15, 2014, at 6:22 PM, Jeff Frost <[email protected]> wrote:
> I'm using slony 2.2.2 to migrate from 8.4 to 9.3 and after the initial sync
> has completed, I'm seeing the following in the slon logs on the subscriber
> (node 2):
>
> 2014-02-16 02:01:19 UTC ERROR remoteListenThread_2: db_getLocalNodeId()
> returned 1 - wrong database?
>
> And indeed, if I run this query on the subscriber:
>
> select "_migration".getlocalnodeid('_migration');
> getlocalnodeid
> ----------------
> 1
> (1 row)
>
> Except it should be node 2.
>
> Is there anyway to fix this without a full resync?
>
> Do I need to revert to 2.2.1 and resync?
> _______________________________________________
> Slony1-general mailing list
> [email protected]
> http://lists.slony.info/mailman/listinfo/slony1-general
---
Jeff Frost <[email protected]>
CTO, PostgreSQL Experts, Inc.
Phone: 1-888-PG-EXPRT x506
FAX: 415-762-5122
http://www.pgexperts.com/
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
