Hi - I've been running slony 2.0.4 in test for a few weeks now.
Just last week we physically moved the machine that houses the master db
To a server block that the slave also resides on. We changed the i/p and
also
Began running with pgpool (port 9999) as the administrator.
It was then that we began throwing the above error. No matter how many
times
I've cleared out sl_nodelock and restarted slon I still get the same error
on
The master postgres log. Reading through the slony docs and entering
bugzilla
For the first time, I come to realize this is a bug that has been fixed.
I'm not a systems administrator so, while I do database upgrades, I'm not as
familiar
With applying patches on existing software and I'm totally new to bugzilla.
Need some
Guidance. Do I:
1. Upgrade to 2.0.5?
2. apply a patch? If so where do I find it?
Thanks for your time,
Mark Steben | Database Administrator
<http://www.autorevenue.com> @utoRevenueR - "Keeping Customers Close"
95D Ashley Ave, West Springfield, MA 01089
413.243.4800 x1512 (Phone) |413.732-1824 (Fax)
<http://www.dominionenterprises.com> @utoRevenue is a registered trademark
and a division of Dominion Enterprises
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
