Re: Run pgAdmin II Slony-I Creation scripts outside of pgAdmin III?
I will do more research using that method. I was planning on allowing a user to run the app on the Master node
and each slave node to allow then to add one slave at a time (due to the fact that we must maintain 100% uptime
in the event of a schema change). That shouldn't be an issue when using Slonik directly, correct?
Shaun McCloud, MCDST | Associate Software Developer
Geo-Comm Inc. | www.geo-comm.com
From: Christopher Browne [mailto:cbbrowne@...]
Sent: Tuesday, May 22, 2012 12:12
To: Shaun McCloud
Subject: Re: [Slony1-general] Run pgAdmin II Slony-I Creation scripts outside of pgAdmin III?
On Tue, May 22, 2012 at 11:36 AM, Shaun McCloud <smccloud@...> wrote:
> Is it possible/feasible to use the Slony-I Creation scripts designed
> for use in pgAdmin III outside of pgAdmin III? I need to write a
> utility to make it easier for our installers to setup Slony-I and I'd
> like to use the official scripts to do it but I'm unsure how to go about it right now.
The last discussion I had (if memory serves, with Dave Page, almost exactly a year ago, at PGcon... If my
memory isn't entirely correct, then it's still Dave Page, still PGcon, but it would be *TWO* years
ago...) indicated that pgAdmin III hasn't been tracking Slony functionality for a *long* time now.
What pgAdmin III *had* been doing was to run some of the Slony stored procedures, effectively duplicating
parts of what is implemented in Slonik (<http://git.postgresql.org/gitweb/?p=slony1-engine.git;a=tree;f=src/slonik;h=819d809475fdd45b3d2d58107ae39d7eb7c77a5d;hb=HEAD>).
Now, what they last duplicated was most likely code from Slony 1.2.
(Hence looking like
There have been rather a lot of changes since version 1.2, and functionality of slonik varies, in ways that
sometimes matter, from version to version to version, and the pgAdmin III devs stopped tracking things
The recommendation in these "modern days" is that cluster management should be done using Slonik scripts,
and for Slony 2.1 and later, that's really rather crucial, as slonik has functionality that wouldn't be
terribly appropriate to even attempt to integrate into pgAdmin III.