[Slony1-general] Delayed replication: Explicitly creating a slony-I backlog, and then telling the slon daemon to replicate changes all at once.

Hello, I'm using slony to power a point-of-sale system - changes in the back-office are replicated amongst tills (subscribers). For business logic reasons, I'd like to be able to create a backlog of changes, and then have the slon daemon replicate all such changes upon being explicitly told to do

Re: [Slony1-general] Delayed replication: Explicitly creating a slony-I backlog, and then telling the slon daemon to replicate changes all at once.

David, Unfortunately, changes to the database may be quite varied. We aren't talking about massive amounts of data though - in the order a few dozen rows per update per slave. Confining that to a single transaction isn't realistic, though. How would I go about applying this horrifically kludgy

Re: [Slony1-general] Delayed replication: Explicitly creating a slony-I backlog, and then telling the slon daemon to replicate changes all at once.

Jan, Artificially delaying the replication process for purposes of point in time recovery was considered in the original design of the Slony-I system, but the mechanism was actually never implemented. The idea was not quite how you describe it above, where slon would wait until some sort of

[Slony1-general] Hybrid MS Windows/ Linux cluster

/master based slon process, with no trace of Slony on the slaves other then the triggers and so on that the Slony configuration script leaves in the node's database? Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info

Re: [Slony1-general] Hybrid MS Windows/ Linux cluster

Windows master, without having the slon daemon running/ configured on the slave nodes, right? Is this best practice? Thanks, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1

[Slony1-general] Replication works for a short while on windows XP, then breaks on restart

Hello, I'm attempting to produce a Slony-I cluster, with a windows XP master and single Linux slave. Though it's probably not relevant, for this test run I'm using virtual machines. I have methodically followed the example in the PgAdminIII documentation, leaving all my slon engines on the

[Slony1-general] Building Slony-I 1.2.15 on Opensuse 11 / i586 causes ld to give error cannot find -lpgport

on how to fix this problem, Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general

Re: [Slony1-general] Building Slony-I 1.2.15 on Opensuse 11 / i586 causes ld to give error cannot find -lpgport

Ian, I think I've figured out what the problem is. The postgresql-devel package with opensuse 10.3 has /usr/lib/libpgport.a . The postgresql-devel with Opensuse 11 doesn't have /usr/lib/libpgport.a . Perhaps I should be complaining elsewhere :-) Regards, Peter Geoghegan

Re: [Slony1-general] Building Slony-I 1.2.15 on Opensuse 11 / i586 causes ld to give error cannot find -lpgport

Here's an interesting new development: http://bugs.archlinux.org/task/11346 This must have been why libpgport.a was missing, Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman

Re: [Slony1-general] Building Slony-I 1.2.15 on Opensuse 11 / i586 causes ld to give error cannot find -lpgport

build service future SUSE releases. Perhaps it would be a good idea to not link libpgport.a (at least on Linux) in future versions of Slony-I. Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http

[Slony1-general] Getting Slony 2.0.2 working on windows vista with PostgreSQL 8.4.0 - No admin conninfo provided for node -1

a node one, because I called init cluster above with id 1? How can the problem be fixed? Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general

[Slony1-general] Re: Getting Slony 2.0.2 working on windows vista with PostgreSQL 8.4.0 - No admin conninfo provided for node -1

consider updating the Replicating your first database page of the docs so others don't repeat my mistake, Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general

Re: [Slony1-general] pgAdmin

), Regards, Peter Geoghegan 2009/7/14 Henrik HJ testt...@live.dk: - Show quoted text - Hi I trying to make a cluster with Slony1 by using pgAdmin. When I try to make a new cluster. I get the Message: Slony-I creation scripts not available; only joining possible. On the pgAdmin file

[Slony1-general] Safely stopping and starting replication using bare metal slony functions

is not suitable for replicating offline nodes that only become available sporadic [sic] for synchronization. 2. If it is sensible, is it possible to achieve the same result through calls to bare metal slony functions? Thanks, Peter Geoghegan ___ Slony1

Re: [Slony1-general] Safely stopping and starting replication using bare metal slony functions

Aleksander, I appreciate the suggestion, but that seems very hacky. I just hoped that there was a simple mechanism for stopping replication using bare metal functions, Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general

[Slony1-general] sl_status incorrectly reports long event lag

make the sl_status view's lag for the slave return to zero by restarting slon daemons. Why might this be? I find the sl_status view very important for my particular application. Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general

Re: [Slony1-general] sl_status incorrectly reports long event lag

is not in fact down to misconfiguration. I'll run those tests tomorrow in work and report back what they find. Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general

Re: [Slony1-general] sl_status incorrectly reports long event lag

no idea why test_slony_state-dbi.pl cannot connect to the two slave nodes's DBs - the databases are plainly present on the nodes - I can connect directly to them from the machine that I'm running the test on, and see everything is in order. Why might this problem occur? Thanks, Peter Geoghegan

Re: [Slony1-general] sl_status incorrectly reports long event lag

host=10.0.0.82 user=postgres password=my_password *isn't* working. I've followed your instructions, and the problem is resolved. Thanks a lot for your help, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http

Re: [Slony1-general] sl_status incorrectly reports long event lag

Any further help you could offer is greatly appreciated, Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general

Re: [Slony1-general] Slony scripts

Hi Can you pleas help me. I try to get pgAdmin III to work with slony, but I can not find the slony modules xxid and slony1_funcs scripts. Where can I get it? Henrik What platform are you doing this on? Regards, Peter Geoghegan ___ Slony1

Re: [Slony1-general] Slony scripts

What operating system? Windows? What PostgreSQL version? What Slony-I version? These are the sorts of details you ought to have included in your first e-mail to have any hope of getting a useful response. Regards, Peter Geoghegan ___ Slony1-general

Re: [Slony1-general] Windows Event Log Error

of?) we might be able to help you. Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general

Re: [Slony1-general] Windows Event Log Error

of that set has its own id, unique to that set. I doubt you'll need more than one set. I seem to recall that if you don't specify the table id in PgAdminIII when adding a table to a set, it will just give you the next available one. Regards, Peter Geoghegan

[Slony1-general] Problem with Slony-I 2.0.2, sl_status persists

pe...@peter-development-machine:~/slony1-2.0.2/tools Any further help you could offer is greatly appreciated, Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general

[Slony1-general] Why does sl_status event lag grow, even though events *are* replicated?

-- Listing of old open connections on node 2 Database PIDUserQuery Age Query pe...@peter-development-machine:~/slony1-2.0.2/tools Why is this happening? Regards, Peter Geoghegan

Re: [Slony1-general] Why does sl_status event lag grow, even though events *are* replicated?

, Afilias Canada Corp. Thanks for letting me know. Is this particular bug (presumably similar to but distinct from the one brad mentions in the 1.1 branch) one that has already been fixed? Can someone suggest a course of action to fix the problem? Regards, Peter Geoghegan

[Slony1-general] Using Slony 2.0.2 with 8.4, Missing autovacuum table, missing entries in sl_status

changes from that revision, is it possible for me to update my Slony stored procedures or something so I don't have this problem? How? Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman

[Slony1-general] Getting benign AFTER triggers to fire on slaves only

see that I can ALTER TABLE my_table ENABLE REPLICA TRIGGER my_trig and get the desired behaviour. Should I just make a point of doing this after replication has been setup on all slaves? I'm using Slony 2.0.2, with Postgres 8.3.5 on the slave and 8.4.1 on the master. Regards, Peter Geoghegan

Re: [slony1-general] slony I 2.0.3

and fixing the problem (I need windows binaries, so I haven't tried 2.3RCs yet). However, I've used 1.2.15 in the past and never had any problems. It might be prudent to stick to 1.2.* if everything is fine already, Regards, Peter Geoghegan ___ Slony1

Re: [slony1-general] slony I 2.0.3

or betas. Had that been the case, I wouldn't have put them into production. That said, I haven't experienced major issues, just minor ones - no show-stoppers. Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http

Re: [Slony1-general] [slony1-general] slony I 2.0.3

as the developers themselves. Unfortunately, attaining that level of understanding isn't an option for most users, myself included. Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman

Re: [Slony1-general] Warning while updating postgres using slony

Hi Nimesh, I'm on 2.0.2, and have found that this error can be safely ignored. I seem to recall reading on slony.info that this unnecessary warning was removed in one of the 2.0.3RCs. In any case, 8.4 is supported by 2.0.2. Regards, Peter Geoghegan

Re: [Slony1-general] Is Slony for me?

this is a non-starter, I would think. Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general

[Slony1-general] How sensible is turning off synchronous_commit on a Slony slave while leaving it on on the master?

synchronous_commit on the slaves but not on the master? Thanks, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general

Re: [Slony1-general] How sensible is turning off synchronous_commit on a Slony slave while leaving it on on the master?

on a session basis. I see that I can: SET synchronous_commit = false; from within my application. This seems far more sensible than forcing asynchronous commit on Slony and other remote clients of my slave dbs, of which there are several. Thanks, Peter Geoghegan

Re: [Slony1-general] How sensible is turning off synchronous_commit on a Slony slave while leaving it on on the master?

it on a per-session basis, so that clients of pg databases that are a slony-I nodes can avail themselves of asynchronous commits where that makes sense. Thanks, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http

Re: [Slony1-general] [Slony1-hackers] Upcoming slony releases

? Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general

Re: [Slony1-general] git ?

of lockstep with PG - I haven't encountered any voices in the wider Postgres community that are lobbying for anything other than git, so there probably aren't any, as has been noted on this thread. Besides, even if that does happen, does that actually matter all that much? Regards, Peter Geoghegan

Re: [Slony1-general] Sending notification on replication problem

an improvement at all. Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general

Re: [Slony1-general] slony + win32

guess is that he'll end up doing this with 2.0.4. -- Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general

Re: [Slony1-general] slony + win32

Hi Peter, Is this installed via the StackBuilder? - Or is it available as a separate download? I'm pretty sure he's talking about StackBuilder. Yes, I am. -- Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general

Re: [Slony1-general] recommendations for removing bloat

Hello, I think you should read the following article about VACUUM FULL before embarking on this: http://it.toolbox.com/blogs/database-soup/getting-rid-of-vacuum-full-feedback-needed-33959 -- Regards, Peter Geoghegan ___ Slony1-general mailing list

Re: [Slony1-general] slony1-2.0.x ready for production?

the release candidate process. Slony 2.0.4 is unaffected (in fact, Slony 2.0.4 is, as far as I know, exactly the same but for the fact that it's unaffected). -- Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http

Re: [Slony1-general] 2.0.6 - 2.0.4?

the trouble that comes with building Slony on windows (you need to use mingw). The bugs fixed in 2.0.5 and 2.0.6 are pretty unlikely to affect you. -- Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http

Re: [Slony1-general] 2.0.6 - 2.0.4?

a little bit before EDB's, but he doesn't anymore. EDB QA their Slony binaries, so I suppose Hiroshi concluded that it was a redundant effort. -- Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info

Re: [Slony1-general] sl_status not updated, despite replication working (slony 2.0.6)

I'm really glad that this bug has finally been fixed! -- Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general

Re: [Slony1-general] How sensible is turning off synchronous_commiton a Slony slave while leaving it on on the master?

Hanif, Slony versions must be *identical*. However, postgres versions can be different major releases. Before pg_upgrade, slony was a popular way of upgrading large databases. -- Regards, Peter Geoghegan ___ Slony1-general mailing list Slony1-general

Re: [Slony1-general] CESTERROR remoteListenThread_1: timeout (300 s) for event selection

are running correctly: http://slony.info/documentation/2.0/monitoring.html This should form part of your monitoring setup. It is common to automatically run the script at regular intervals. -- Peter Geoghegan       http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training

Re: [Slony1-general] pg_dump and replication lag in 2.0.7

option was added to pg_dump specifically to facilitate Slony users. -- Peter Geoghegan       http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training and Services ___ Slony1-general mailing list Slony1-general@lists.slony.info http