gmane.comp.db.postgresql.slony1.general http://blog.gmane.org/gmane.comp.db.postgresql.slony1.general hourly 1 1901-01-01T00:00+00:00 Gmane http://gmane.org/img/gmane-25t.png http://gmane.org slony.info website outage http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10722 <pre>The slony.info website will be taken offline for maintenance on: Wednesday, May 23 starting at 7:30pm * The website - www.slony.info * The slony bugzilla instance * All slony mailing lists will be offline, this is expected to last a few hours. Thanks </pre> Steve Singer 2012-05-22T21:23:59 Run pgAdmin II Slony-I Creation scripts outside ofpgAdmin III? http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10717 <pre>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. Shaun McCloud, MCDST | Associate Software Developer Geo-Comm Inc. | www.geo-comm.com&lt;http://www.geo-comm.com/&gt; 601 W. Saint Germain St., St. Cloud, MN, 56301 Office: 320.240.0040 or 888.436.2666 Fax: 320.240.2389 _______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> Shaun McCloud 2012-05-22T15:36:13 slony upstart script for Ubuntu 10.04+ http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10712 <pre>I wrote an upstart script for starting slony on ubuntu 10.04+. If there's any interest in including it in the slony distro, you can find it here: https://github.com/pgexperts/upstart-scripts/blob/master/etc/init/slony.conf </pre> Jeff Frost 2012-05-15T21:52:44 Error finding slony1_funcs http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10711 <pre>Not sure what I'm missing but I get this error when I try to run the slony config. I'm running this at postgres. I ran the config earlier this week and we had to stop slony. Try to run it today but fails $ ./slony-conf.sh &lt;stdin&gt;:21: PGRES_FATAL_ERROR load '$libdir/slony1_funcs'; - ERROR: could not access file "$libdir/slony1_funcs": No such file or directory &lt;stdin&gt;:21: Error: the extension for the Slony-I C functions cannot be loaded in database 'dbname=canvas_db host=harv user=postgres' It all looks correct but can't find slony1_funcs when running conf $ find /opt/postgres -name slony1_funcs.so /opt/postgres/9.0.3-pgdg/lib/slony1_funcs.so $ pg_config --libdir /opt/postgres/9.0.3-pgdg/lib $ pg_config --pkglibdir /opt/postgres/9.0.3-pgdg/lib $ ll /opt/postgres/9.0.3-pgdg/lib/slony1_funcs.so -rwxr-xr-x 1 postgres postgres 39K Apr 9 14:28 /opt/postgres/9.0.3-pgdg/lib/slony1_funcs.so 0___ Wolfgang Schwurack c/ /'_ SA/DBA - UEN (*) \(*) 801-587-9444 wolf-OzwJb8Xg5oY&lt; at &gt;public.gmane.org </pre> Wolf Schwurack 2012-05-12T01:42:38 some questions which popped up while setting up... http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10699 <pre>Hey all! I successfully setup my first slony replication - however quite a few conceptual questions raised on the way: I have the following setup (taken from slon_tools.conf): add_node(node =&gt; 1, host =&gt; 'master.foo', dbname =&gt; 'foo', port =&gt; 5432, user =&gt; 'slony', password =&gt; 'XXX'); add_node(node =&gt; 11, host =&gt; 'slave1.foo', dbname =&gt; 'foo', port =&gt; 6254, user =&gt; 'slony', password =&gt; 'XXX'); add_node(node =&gt; 12, host =&gt; 'slave2.foo', dbname =&gt; 'foo', port =&gt; 2254, user =&gt; 'slony', password =&gt; 'XXX'); This config got deployed on every node, every pg_hba.conf-file contained a line which allowed all other servers to connect as user slony. Everything was working - until I tried to optimize. I thought, well, there needs to be a connection between the master and the slaves but no direct connection between the slaves - so I dropped the access lines in pg_hba.conf on the slaves for the other slave respectively. The setup seemed to still work, however on the slaves I noticed error messages like: FATAL: no pg_hba.conf entry for host "slave1.foo", user "slony", database "foo" Okay, fine, obviously they try to connect to each other: so I purged out the respective node-definitions out of the slon_tools.conf file on the slaves (on node 11 I deleted the definition of node 12 and vice versa). After restarting slony the slaves still tried to connect to each other. Where do they have the connect information from? And why are they trying to connect to each other at all? Anyway, next thought: if one node gets hacked the attacker shouldn't be able to access the database on the other nodes. Idea was: The slaves do not need to access the master with a user who has write access to that database (slony). That's why I created a read-only user on the master (slony_ro) and tried to tell the slaves - by changing the user 'slony' to 'slony_ro' within the slon_tools.conf-files - to connect as 'slony_ro'. However also that change didn't show any effect after restarting slony. It seems to me - by initializing the cluster, creating and subscribing to the going-to-be-replicated sets - the information got pushed to the slaves from the master. That raises 2 (sub-)questions: a) Where is this information stored? b) why there is the need of a slon_tools.conf file if its data is not used anyway (at least on the slaves)? Maybe somebody could lighten me up here? I didn't find any information able to clear my confusion about that yet :/ Cheers, thanks a lot in advance and have a nice week! mirko </pre> Mirko Vogt 2012-04-24T14:40:08 New to slony http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10697 <pre>I am getting this error..i dont know where to change..can anyone say.. &lt;stdin&gt;:8: loading of file /usr/local/pgsql/share//slony1_funcs.sql: PGRES_FATAL_ERROR ERROR: Slonik version: 2.0.6 != Slony-I version in PG build 2.1.1 ERROR: Slonik version: 2.0.6 != Slony-I version in PG build 2.1.1 _______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> Lakshmi Priya 2012-04-12T10:39:38 Update function http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10696 <pre>When i specify UPDATE FUNCTIONS ( ID = 3 # Update functions on node 3 ); I am getting event node error,even i specified event node as 2 or 3. Event node function will not work in update node. Can anyone help me.. _______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> Lakshmi Priya 2012-04-12T06:11:10 Logship files printing incorrectly http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10694 <pre>Hi, I've recently come across a situation where slony logshipping files were being written incorrectly. Normally, the files are written in this order: - Begin transaction - Set archive tracking index - INSERTs/UPDATEs/DELETEs - Set sequences - Vacuum - Commit I noticed that in my particular instance, the files were being written as such: - Begin transaction - Set archive tracking index - Vacuum - Commit - INSERTs/UPDATEs/DELETEs - Set sequences Obviously, this sounds pretty dangerous, and I actually encountered the situation where my logship destination got corrupted, and needed to rebuild that node. Would anyone have any insight into why this happens? Using 2.0.6 on CentOS, with Postgres 8.4.5 Thanks! --Richard _______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> Richard Yen 2012-04-11T13:24:37 Error in slony http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10688 <pre>Can any one say what this error meant..?? &lt;stdin&gt;:8: loading of file /usr/local/pgsql/share//slony1_funcs.sql: PGRES_FATAL_ERROR ERROR: Slonik version: 2.0.6 != Slony-I version in PG build 2.1.1. _______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> Lakshmi Priya 2012-04-11T07:24:46 Can you delete rows from the slave database? http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10685 <pre> If I am replicating from one database to another, can I delete rows from the slave database and not have Slony re-populate those rows (provided the rows in the master database have not been updated)? </pre> NewToSlony 2012-04-11T03:59:20 cleanup_interval http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10683 <pre>How do you change the cleanup_interval option on a Windows cluster? I have tried adding it to the engine file and that doesn't change anything and everything I've found online shows how to do it in a *NIX cluster, not a Windows one. Shaun McCloud - Associate Software Developer Geo-Comm, Inc 601 W. Saint Germain St., Saint Cloud, MN 56301 Office: 320.240.0040 Fax: 320.240.2389 Toll Free: 888.436.2666 click here to visit www.geo-comm.com&lt;http://www.geo-comm.com/&gt; [cid:image001.jpg-6jK/KXen6uTyw+Oj8IRwQDRmByFHzeGd&lt; at &gt;public.gmane.org]&lt;http://www.linkedin.com/companies/geocomm&gt; [cid:image002.jpg-6jK/KXen6uTyw+Oj8IRwQDRmByFHzeGd&lt; at &gt;public.gmane.org] &lt;http://twitter.com/_geocomm&gt; P Think before you print! Microsoft Certified Desktop Support Technician (MCDST) _______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> Shaun McCloud 2012-04-10T20:49:30 confusing sl_status output and replication stalled http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10681 <pre>Yesterday I set up a DB to replicate. It was previously set up with slony 1.2 but the backup server died, so I took the opportunity to move to 2.1. I did the dropnode and uninstallnode to clean up the master. I followed my normal, init, create set, subscribe sequence that has always worked. I had done the same thing about a week ago with the other DB on this same server pair. When I left work yesterday, it was dutifully copying the DB. This morning I went to check and the master has not generated an event since 2012-04-10 05:35:49.782917-04. The sl_status on the master shows this: -[ RECORD 1 ]-------------+------------------------------ st_origin | 20 st_received | 31 st_last_event | 5000008023 st_last_event_ts | 2012-04-10 05:35:49.782917-04 st_last_received | 5000008023 st_last_received_ts | 2012-04-10 05:35:50.00566-04 st_last_received_event_ts | 2012-04-10 05:35:49.782917-04 st_lag_num_events | 0 st_lag_time | 04:27:58.674963 I verified that no replication is flowing by updating one row in a table. The lag_time and lag_num_events seem to be contradictory to me. The logs on the master show nothing exciting at this timestamp. In fact, the whole of the logs I have (which only go back to about 10pm last night), says basically this: 2012-04-09 21:51:17.872892500 DEBUG1 calc sync size - last time: 1 last length: 18010 ideal: 3 proposed size: 3 2012-04-09 21:51:17.873042500 DEBUG1 remoteWorkerThread_31: no sets need syncing for this event 2012-04-09 21:51:19.876883500 DEBUG1 calc sync size - last time: 1 last length: 2003 ideal: 29 proposed size: 3 2012-04-09 21:51:19.877031500 DEBUG1 remoteWorkerThread_31: no sets need syncing for this event This is logged over and over and over. The "length" is slightly different on each log, but only by a few. The logs on the replica at the time of the last event shown in the status line are shown below. There is nothing remarkable in the postgres.log files around this time, either. Restarting slons on both ends did not change anything. Versions: Origin: FreeBSD 7.2, slony1 2.1.1, postgres 8.3.18 Replica: FreeBSD 9.0, slony1 2.1.1, postgres 9.1.3 I'm pretty sure I did not do anything incorrectly. The DB I set up to replicate on this pair of machines last week is properly replicating still. What should I look to fix? The DB is small enough that re-starting from scratch is not out of the question. Logs from replica up to the point I restarted it: 2012-04-10 05:34:49.969486500 DEBUG1 calc sync size - last time: 1 last length: 2003 ideal: 29 proposed size: 3 2012-04-10 05:34:49.970585500 DEBUG1 about to monitor_subscriber_query - pulling big actionid list for 20 2012-04-10 05:34:49.973240500 INFO remoteWorkerThread_20: syncing set 1 with 52 table(s) from provider 20 2012-04-10 05:34:49.976524500 DEBUG1 remoteHelperThread_20_20: 0.002 seconds delay for first row 2012-04-10 05:34:49.977010500 DEBUG1 remoteHelperThread_20_20: 0.003 seconds until close cursor 2012-04-10 05:34:49.977028500 DEBUG1 remoteHelperThread_20_20: inserts=0 updates=0 deletes=0 truncates=0 2012-04-10 05:34:49.977031500 DEBUG1 remoteWorkerThread_20: sync_helper timing: pqexec (s/count)- provider 0.003/3 - subscriber 0.000/3 2012-04-10 05:34:49.977035500 DEBUG1 remoteWorkerThread_20: sync_helper timing: large tuples 0.000/0 2012-04-10 05:34:49.978175500 INFO remoteWorkerThread_20: SYNC 5000008017 done in 0.008 seconds 2012-04-10 05:34:49.978202500 DEBUG1 remoteWorkerThread_20: SYNC 5000008017 sync_event timing: pqexec (s/count)- provider 0.001/2 - subscriber 0.004/2 - IUD 0.000/0 2012-04-10 05:35:07.978560500 DEBUG1 calc sync size - last time: 1 last length: 18009 ideal: 3 proposed size: 3 2012-04-10 05:35:07.979742500 DEBUG1 about to monitor_subscriber_query - pulling big actionid list for 20 2012-04-10 05:35:07.982419500 INFO remoteWorkerThread_20: syncing set 1 with 52 table(s) from provider 20 2012-04-10 05:35:07.985717500 DEBUG1 remoteHelperThread_20_20: 0.002 seconds delay for first row 2012-04-10 05:35:07.986202500 DEBUG1 remoteHelperThread_20_20: 0.003 seconds until close cursor 2012-04-10 05:35:07.986226500 DEBUG1 remoteHelperThread_20_20: inserts=0 updates=0 deletes=0 truncates=0 2012-04-10 05:35:07.986228500 DEBUG1 remoteWorkerThread_20: sync_helper timing: pqexec (s/count)- provider 0.003/3 - subscriber 0.000/3 2012-04-10 05:35:07.986232500 DEBUG1 remoteWorkerThread_20: sync_helper timing: large tuples 0.000/0 2012-04-10 05:35:07.987233500 INFO remoteWorkerThread_20: SYNC 5000008018 done in 0.008 seconds 2012-04-10 05:35:07.987250500 DEBUG1 remoteWorkerThread_20: SYNC 5000008018 sync_event timing: pqexec (s/count)- provider 0.001/2 - subscriber 0.004/2 - IUD 0.000/0 2012-04-10 05:35:09.981610500 DEBUG1 calc sync size - last time: 1 last length: 2003 ideal: 29 proposed size: 3 2012-04-10 05:35:09.982726500 DEBUG1 about to monitor_subscriber_query - pulling big actionid list for 20 2012-04-10 05:35:09.985421500 INFO remoteWorkerThread_20: syncing set 1 with 52 table(s) from provider 20 2012-04-10 05:35:09.988536500 DEBUG1 remoteHelperThread_20_20: 0.002 seconds delay for first row 2012-04-10 05:35:09.989020500 DEBUG1 remoteHelperThread_20_20: 0.003 seconds until close cursor 2012-04-10 05:35:09.989044500 DEBUG1 remoteHelperThread_20_20: inserts=0 updates=0 deletes=0 truncates=0 2012-04-10 05:35:09.989047500 DEBUG1 remoteWorkerThread_20: sync_helper timing: pqexec (s/count)- provider 0.002/3 - subscriber 0.000/3 2012-04-10 05:35:09.989050500 DEBUG1 remoteWorkerThread_20: sync_helper timing: large tuples 0.000/0 2012-04-10 05:35:09.990168500 INFO remoteWorkerThread_20: SYNC 5000008019 done in 0.008 seconds 2012-04-10 05:35:09.990190500 DEBUG1 remoteWorkerThread_20: SYNC 5000008019 sync_event timing: pqexec (s/count)- provider 0.001/2 - subscriber 0.004/2 - IUD 0.000/0 2012-04-10 05:35:27.990339500 DEBUG1 calc sync size - last time: 1 last length: 18008 ideal: 3 proposed size: 3 2012-04-10 05:35:27.991575500 DEBUG1 about to monitor_subscriber_query - pulling big actionid list for 20 2012-04-10 05:35:27.994443500 INFO remoteWorkerThread_20: syncing set 1 with 52 table(s) from provider 20 2012-04-10 05:35:27.997586500 DEBUG1 remoteHelperThread_20_20: 0.002 seconds delay for first row 2012-04-10 05:35:27.998073500 DEBUG1 remoteHelperThread_20_20: 0.003 seconds until close cursor 2012-04-10 05:35:27.998098500 DEBUG1 remoteHelperThread_20_20: inserts=0 updates=0 deletes=0 truncates=0 2012-04-10 05:35:27.998100500 DEBUG1 remoteWorkerThread_20: sync_helper timing: pqexec (s/count)- provider 0.002/3 - subscriber 0.000/3 2012-04-10 05:35:27.998124500 DEBUG1 remoteWorkerThread_20: sync_helper timing: large tuples 0.000/0 2012-04-10 05:35:27.999188500 INFO remoteWorkerThread_20: SYNC 5000008020 done in 0.009 seconds 2012-04-10 05:35:27.999206500 DEBUG1 remoteWorkerThread_20: SYNC 5000008020 sync_event timing: pqexec (s/count)- provider 0.001/2 - subscriber 0.004/2 - IUD 0.000/0 2012-04-10 05:35:29.994615500 DEBUG1 calc sync size - last time: 1 last length: 2004 ideal: 29 proposed size: 3 2012-04-10 05:35:29.995579500 DEBUG1 about to monitor_subscriber_query - pulling big actionid list for 20 2012-04-10 05:35:29.998284500 INFO remoteWorkerThread_20: syncing set 1 with 52 table(s) from provider 20 2012-04-10 05:35:30.001519500 DEBUG1 remoteHelperThread_20_20: 0.002 seconds delay for first row 2012-04-10 05:35:30.002015500 DEBUG1 remoteHelperThread_20_20: 0.003 seconds until close cursor 2012-04-10 05:35:30.002041500 DEBUG1 remoteHelperThread_20_20: inserts=0 updates=0 deletes=0 truncates=0 2012-04-10 05:35:30.002043500 DEBUG1 remoteWorkerThread_20: sync_helper timing: pqexec (s/count)- provider 0.003/3 - subscriber 0.000/3 2012-04-10 05:35:30.002071500 DEBUG1 remoteWorkerThread_20: sync_helper timing: large tuples 0.000/0 2012-04-10 05:35:30.003135500 INFO remoteWorkerThread_20: SYNC 5000008021 done in 0.008 seconds 2012-04-10 05:35:30.003153500 DEBUG1 remoteWorkerThread_20: SYNC 5000008021 sync_event timing: pqexec (s/count)- provider 0.001/2 - subscriber 0.004/2 - IUD 0.000/0 2012-04-10 05:35:48.002553500 DEBUG1 calc sync size - last time: 1 last length: 18008 ideal: 3 proposed size: 3 2012-04-10 05:35:48.003694500 DEBUG1 about to monitor_subscriber_query - pulling big actionid list for 20 2012-04-10 05:35:48.006392500 INFO remoteWorkerThread_20: syncing set 1 with 52 table(s) from provider 20 2012-04-10 05:35:48.010208500 DEBUG1 remoteHelperThread_20_20: 0.003 seconds delay for first row 2012-04-10 05:35:48.010704500 DEBUG1 remoteHelperThread_20_20: 0.003 seconds until close cursor 2012-04-10 05:35:48.010727500 DEBUG1 remoteHelperThread_20_20: inserts=0 updates=0 deletes=0 truncates=0 2012-04-10 05:35:48.010730500 DEBUG1 remoteWorkerThread_20: sync_helper timing: pqexec (s/count)- provider 0.003/3 - subscriber 0.000/3 2012-04-10 05:35:48.010760500 DEBUG1 remoteWorkerThread_20: sync_helper timing: large tuples 0.000/0 2012-04-10 05:35:48.011887500 INFO remoteWorkerThread_20: SYNC 5000008022 done in 0.009 seconds 2012-04-10 05:35:48.011905500 DEBUG1 remoteWorkerThread_20: SYNC 5000008022 sync_event timing: pqexec (s/count)- provider 0.001/2 - subscriber 0.004/2 - IUD 0.000/0 2012-04-10 05:35:50.005622500 DEBUG1 calc sync size - last time: 1 last length: 2003 ideal: 29 proposed size: 3 2012-04-10 05:35:50.006807500 DEBUG1 about to monitor_subscriber_query - pulling big actionid list for 20 2012-04-10 05:35:50.009542500 INFO remoteWorkerThread_20: syncing set 1 with 52 table(s) from provider 20 2012-04-10 05:35:50.012900500 DEBUG1 remoteHelperThread_20_20: 0.002 seconds delay for first row 2012-04-10 05:35:50.013507500 DEBUG1 remoteHelperThread_20_20: 0.003 seconds until close cursor 2012-04-10 05:35:50.013532500 DEBUG1 remoteHelperThread_20_20: inserts=0 updates=0 deletes=0 truncates=0 2012-04-10 05:35:50.013535500 DEBUG1 remoteWorkerThread_20: sync_helper timing: pqexec (s/count)- provider 0.002/3 - subscriber 0.000/3 2012-04-10 05:35:50.013538500 DEBUG1 remoteWorkerThread_20: sync_helper timing: large tuples 0.000/0 2012-04-10 05:35:50.014538500 INFO remoteWorkerThread_20: SYNC 5000008023 done in 0.009 seconds 2012-04-10 05:35:50.014566500 DEBUG1 remoteWorkerThread_20: SYNC 5000008023 sync_event timing: pqexec (s/count)- provider 0.001/2 - subscriber 0.004/2 - IUD 0.000/0 2012-04-10 05:42:49.135088500 NOTICE: Slony-I: Logswitch to sl_log_1 initiated 2012-04-10 05:42:49.135091500 CONTEXT: SQL statement "SELECT "_listserver".logswitch_start()" 2012-04-10 05:42:49.135093500 PL/pgSQL function "cleanupevent" line 96 at PERFORM 2012-04-10 05:42:49.136708500 INFO cleanupThread: 0.007 seconds for cleanupEvent() 2012-04-10 05:42:49.137023500 DEBUG1 cleanupThread: minxid: 914784 2012-04-10 05:42:49.148330500 DEBUG1 cleanupThread: number of tables to clean: 0 2012-04-10 05:42:49.148355500 INFO cleanupThread: 0.011 seconds for vacuuming 2012-04-10 05:53:12.962525500 NOTICE: Slony-I: log switch to sl_log_1 complete - truncate sl_log_2 2012-04-10 05:53:12.962529500 CONTEXT: PL/pgSQL function "cleanupevent" line 94 at assignment 2012-04-10 05:53:12.998818500 INFO cleanupThread: 0.042 seconds for cleanupEvent() 2012-04-10 06:04:36.665595500 NOTICE: Slony-I: Logswitch to sl_log_2 initiated 2012-04-10 06:04:36.665599500 CONTEXT: SQL statement "SELECT "_listserver".logswitch_start()" 2012-04-10 06:04:36.665601500 PL/pgSQL function "cleanupevent" line 96 at PERFORM 2012-04-10 06:04:36.666893500 INFO cleanupThread: 0.006 seconds for cleanupEvent() 2012-04-10 06:15:29.657504500 NOTICE: Slony-I: log switch to sl_log_2 complete - truncate sl_log_1 2012-04-10 06:15:29.657508500 CONTEXT: PL/pgSQL function "cleanupevent" line 94 at assignment 2012-04-10 06:15:29.762306500 INFO cleanupThread: 0.111 seconds for cleanupEvent() 2012-04-10 06:15:29.762954500 DEBUG1 cleanupThread: minxid: 917868 2012-04-10 06:15:29.776761500 DEBUG1 cleanupThread: number of tables to clean: 0 2012-04-10 06:15:29.776800500 INFO cleanupThread: 0.014 seconds for vacuuming 2012-04-10 06:26:16.397469500 NOTICE: Slony-I: Logswitch to sl_log_1 initiated 2012-04-10 06:26:16.397472500 CONTEXT: SQL statement "SELECT "_listserver".logswitch_start()" 2012-04-10 06:26:16.397475500 PL/pgSQL function "cleanupevent" line 96 at PERFORM 2012-04-10 06:26:16.413889500 INFO cleanupThread: 0.021 seconds for cleanupEvent() 2012-04-10 06:37:55.058224500 NOTICE: Slony-I: log switch to sl_log_1 complete - truncate sl_log_2 2012-04-10 06:37:55.058227500 CONTEXT: PL/pgSQL function "cleanupevent" line 94 at assignment 2012-04-10 06:37:55.095899500 INFO cleanupThread: 0.045 seconds for cleanupEvent() 2012-04-10 06:48:22.843065500 NOTICE: Slony-I: Logswitch to sl_log_2 initiated 2012-04-10 06:48:22.843069500 CONTEXT: SQL statement "SELECT "_listserver".logswitch_start()" 2012-04-10 06:48:22.843071500 PL/pgSQL function "cleanupevent" line 96 at PERFORM 2012-04-10 06:48:22.844274500 INFO cleanupThread: 0.007 seconds for cleanupEvent() 2012-04-10 06:48:22.844680500 DEBUG1 cleanupThread: minxid: 921509 2012-04-10 06:48:22.858273500 DEBUG1 cleanupThread: number of tables to clean: 0 2012-04-10 06:48:22.858310500 INFO cleanupThread: 0.014 seconds for vacuuming 2012-04-10 06:59:57.970356500 NOTICE: Slony-I: log switch to sl_log_2 complete - truncate sl_log_1 2012-04-10 06:59:57.970359500 CONTEXT: PL/pgSQL function "cleanupevent" line 94 at assignment 2012-04-10 06:59:58.030446500 INFO cleanupThread: 0.066 seconds for cleanupEvent() 2012-04-10 07:11:06.624593500 NOTICE: Slony-I: Logswitch to sl_log_1 initiated 2012-04-10 07:11:06.624596500 CONTEXT: SQL statement "SELECT "_listserver".logswitch_start()" 2012-04-10 07:11:06.624598500 PL/pgSQL function "cleanupevent" line 96 at PERFORM 2012-04-10 07:11:06.626036500 INFO cleanupThread: 0.006 seconds for cleanupEvent() 2012-04-10 07:21:41.656625500 NOTICE: Slony-I: log switch to sl_log_1 complete - truncate sl_log_2 2012-04-10 07:21:41.656628500 CONTEXT: PL/pgSQL function "cleanupevent" line 94 at assignment 2012-04-10 07:21:41.743337500 INFO cleanupThread: 0.092 seconds for cleanupEvent() 2012-04-10 07:21:41.744003500 DEBUG1 cleanupThread: minxid: 924619 2012-04-10 07:21:41.756041500 DEBUG1 cleanupThread: number of tables to clean: 0 2012-04-10 07:21:41.756077500 INFO cleanupThread: 0.012 seconds for vacuuming 2012-04-10 07:33:27.381353500 NOTICE: Slony-I: Logswitch to sl_log_2 initiated 2012-04-10 07:33:27.381356500 CONTEXT: SQL statement "SELECT "_listserver".logswitch_start()" 2012-04-10 07:33:27.381358500 PL/pgSQL function "cleanupevent" line 96 at PERFORM 2012-04-10 07:33:27.389331500 INFO cleanupThread: 0.013 seconds for cleanupEvent() 2012-04-10 07:45:16.467253500 NOTICE: Slony-I: log switch to sl_log_2 complete - truncate sl_log_1 2012-04-10 07:45:16.467256500 CONTEXT: PL/pgSQL function "cleanupevent" line 94 at assignment 2012-04-10 07:45:16.527380500 INFO cleanupThread: 0.066 seconds for cleanupEvent() 2012-04-10 07:57:08.352485500 NOTICE: Slony-I: Logswitch to sl_log_1 initiated 2012-04-10 07:57:08.352488500 CONTEXT: SQL statement "SELECT "_listserver".logswitch_start()" 2012-04-10 07:57:08.352493500 PL/pgSQL function "cleanupevent" line 96 at PERFORM 2012-04-10 07:57:08.353528500 INFO cleanupThread: 0.005 seconds for cleanupEvent() 2012-04-10 07:57:08.353792500 DEBUG1 cleanupThread: minxid: 928158 2012-04-10 07:57:08.364604500 DEBUG1 cleanupThread: number of tables to clean: 0 2012-04-10 07:57:08.364624500 INFO cleanupThread: 0.011 seconds for vacuuming 2012-04-10 08:08:19.444508500 NOTICE: Slony-I: log switch to sl_log_1 complete - truncate sl_log_2 2012-04-10 08:08:19.444512500 CONTEXT: PL/pgSQL function "cleanupevent" line 94 at assignment 2012-04-10 08:08:19.497679500 INFO cleanupThread: 0.062 seconds for cleanupEvent() 2012-04-10 08:20:02.446460500 NOTICE: Slony-I: Logswitch to sl_log_2 initiated 2012-04-10 08:20:02.446463500 CONTEXT: SQL statement "SELECT "_listserver".logswitch_start()" 2012-04-10 08:20:02.446464500 PL/pgSQL function "cleanupevent" line 96 at PERFORM 2012-04-10 08:20:02.447564500 INFO cleanupThread: 0.006 seconds for cleanupEvent() 2012-04-10 08:30:26.285213500 NOTICE: Slony-I: log switch to sl_log_2 complete - truncate sl_log_1 2012-04-10 08:30:26.285216500 CONTEXT: PL/pgSQL function "cleanupevent" line 94 at assignment 2012-04-10 08:30:26.322580500 INFO cleanupThread: 0.043 seconds for cleanupEvent() 2012-04-10 08:30:26.323128500 DEBUG1 cleanupThread: minxid: 931518 2012-04-10 08:30:26.335580500 DEBUG1 cleanupThread: number of tables to clean: 0 2012-04-10 08:30:26.335616500 INFO cleanupThread: 0.012 seconds for vacuuming 2012-04-10 08:41:27.217247500 NOTICE: Slony-I: Logswitch to sl_log_1 initiated 2012-04-10 08:41:27.217250500 CONTEXT: SQL statement "SELECT "_listserver".logswitch_start()" 2012-04-10 08:41:27.217252500 PL/pgSQL function "cleanupevent" line 96 at PERFORM 2012-04-10 08:41:27.218533500 INFO cleanupThread: 0.006 seconds for cleanupEvent() 2012-04-10 08:52:47.346424500 NOTICE: Slony-I: log switch to sl_log_1 complete - truncate sl_log_2 2012-04-10 08:52:47.346427500 CONTEXT: PL/pgSQL function "cleanupevent" line 94 at assignment 2012-04-10 08:52:47.383147500 INFO cleanupThread: 0.041 seconds for cleanupEvent() 2012-04-10 09:03:05.473715500 NOTICE: Slony-I: Logswitch to sl_log_2 initiated 2012-04-10 09:03:05.473719500 CONTEXT: SQL statement "SELECT "_listserver".logswitch_start()" 2012-04-10 09:03:05.473721500 PL/pgSQL function "cleanupevent" line 96 at PERFORM 2012-04-10 09:03:05.474930500 INFO cleanupThread: 0.007 seconds for cleanupEvent() 2012-04-10 09:03:05.475164500 DEBUG1 cleanupThread: minxid: 934871 2012-04-10 09:03:05.485908500 DEBUG1 cleanupThread: number of tables to clean: 0 2012-04-10 09:03:05.485928500 INFO cleanupThread: 0.011 seconds for vacuuming 2012-04-10 09:13:34.729921500 NOTICE: Slony-I: log switch to sl_log_2 complete - truncate sl_log_1 2012-04-10 09:13:34.729924500 CONTEXT: PL/pgSQL function "cleanupevent" line 94 at assignment 2012-04-10 09:13:34.766498500 INFO cleanupThread: 0.043 seconds for cleanupEvent() 2012-04-10 09:25:15.279623500 NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=36103 2012-04-10 09:25:15.279626500 CONTEXT: SQL statement "SELECT "_listserver".cleanupNodelock()" 2012-04-10 09:25:15.279628500 PL/pgSQL function "cleanupevent" line 82 at PERFORM 2012-04-10 09:25:15.281075500 NOTICE: Slony-I: Logswitch to sl_log_1 initiated 2012-04-10 09:25:15.281078500 CONTEXT: SQL statement "SELECT "_listserver".logswitch_start()" 2012-04-10 09:25:15.281079500 PL/pgSQL function "cleanupevent" line 96 at PERFORM 2012-04-10 09:25:15.282365500 INFO cleanupThread: 0.007 seconds for cleanupEvent() 2012-04-10 09:25:30.415269500 CONFIG slon: child terminated signal: 9; pid: 58636, current worker pid: 58636 2012-04-10 09:25:30.415273500 INFO slon: done 2012-04-10 09:25:30.415275500 INFO slon: exit(0) </pre> Vick Khera 2012-04-10T14:24:15 Query to see when Slony is done replicatingchanges? http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10672 <pre>Hello, I'm wondering if its possible to query any of the databases in my cluster to see when Slony is done replicating changes to a single node. I was going to use the Acks Outstanding statistic but then realized that the slave nodes that my controller service is waiting to update (and do not have Slony running on) will keep adding to that count. If there is no statistic to query, is my assumption that tables are replicated in the order they are added to the replication set correct? As for why I can't just let the changes replicate to all slaves at once, it is because of a no single point of failure for the web app that is reading the replicated data. Shaun McCloud - Associate Software Developer Geo-Comm, Inc 601 W. Saint Germain St., Saint Cloud, MN 56301 Office: 320.240.0040 Fax: 320.240.2389 Toll Free: 888.436.2666 click here to visit www.geo-comm.com&lt;http://www.geo-comm.com/&gt; [cid:image001.jpg-HfuTfBXPlMx1/i14CW9yTzRmByFHzeGd&lt; at &gt;public.gmane.org]&lt;http://www.linkedin.com/companies/geocomm&gt; [cid:image002.jpg-HfuTfBXPlMx1/i14CW9yTzRmByFHzeGd&lt; at &gt;public.gmane.org] &lt;http://twitter.com/_geocomm&gt; P Think before you print! Microsoft Certified Desktop Support Technician (MCDST) _______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> Shaun McCloud 2012-04-03T17:51:58 Fix manual http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10668 <pre>Can someone fix the manual for clone finish: http://main.slony.info/documentation/stmtclonefinish.html The synopsis is still using "Clone prepare" instead of "Clone finish"_______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> Brian Trudal 2012-03-30T02:44:36 slony errors on solaris10 http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10667 <pre>I have been trying to compile slony1-2.1.1 on solaris 10 but fails. I got this error on make: "gcc: unrecognized option `-pthread'" So I removed the -pthread from the configure file Now getting: misc.c: In function `slon_log': misc.c:183: warning: int format, pid_t arg )arg 3) misc.c: In function `slon_scanint64' misc.c 268 warning: integer constant is too large for "long" type OS = Solaris 10 slony = slony1-2.1.1 GCC = 3.4.6 Postgres = 9.1.2 0___ Wolfgang Schwurack c/ /'_ SA/DBA - UEN (*) \(*) 801-587-9444 wolf-OzwJb8Xg5oY&lt; at &gt;public.gmane.org </pre> Wolf Schwurack 2012-03-29T15:42:33 CLONE prepare http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10666 <pre>Hi there I couldn't get much info from docs; can someone explain what CLONE PREPARE does ? Essentially I wanted to clone a subscriber1 to new subscriber3; but wanted to confirm; after the clone prepare; does the first subscriber1 will stop replicating from origin or it will continue to replicate ? What happens to other subscribers in the origin node if there are more than one subscribers already ? Also, do we need to skip the dumping of slony schema (_{clustername}) during the dump + restore while cloning new subscriber ? -- brian _______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> Brian Trudal 2012-03-27T20:48:14 Problem with Slony implementation of PostGIS http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10664 <pre>(I am sending this to both the PostGIS and Slony support lists as I am not sure of the correct location). I have run into a problem with how PostGIS and Slony are reacting with each other. Let me say upfront, I am a PostGIS newbee and know just about nothing about Slony. And I know this email is long, but I want to make sure I included everything. This is on a Posgtres 8.3.1, PostGIS 1.3, and Slony 1.2.20 I created a PostGIS table like this: create table b_temp as select 11459815 as msg_no, 0 as rev_no, GeometryFromText('POLYGON((1 1, 2 2, 3 3, 1 1))') as geom1, GeometryFromText('POLYGON((1 1, 2 2, 3 3, 3 3, 1 1))') as geom2; Notice that geom2 has a repeated point of geom1, but other than that they are the same: select geom1 = geom2, ST_Equals(geom1, geom2), ST_OrderingEquals(geom1, geom2) from b_temp; ?column? | st_equals | st_orderingequals ----------+-----------+------------------- t | t | f I then slon'd this table to another node, but didn't start slony on the other node so I could look at slony log tables. Apparently, on an update, slon looks at the data before and after and compares if anything has changed. Then sets the update command for the second node appropriately. Say for example: update b_temp set rev_no = 1; Looking in sl_log_1, I see: log_origin | log_xid | log_tableid | log_actionseq | log_cmdtype | log_cmddata ------------+----------+-------------+---------------+-------------+---------------------------------------------------------- 1 | 82987244 | 217 | 55210696 | U | "rev_no"='1' where "msg_no"='11459815' and "rev_no"='0' That is about what I expected. Things get interesting if you do a non-update. For example, do this: update b_temp set rev_no = 1; Looking in sl_log_1, I see: log_origin | log_xid | log_tableid | log_actionseq | log_cmdtype | log_cmddata ------------+----------+-------------+---------------+-------------+---------------------------------------------------------------- 1 | 82987244 | 217 | 55210696 | U | "msg_no"='11459815'where "msg_no"='11459815' and "rev_no"='0' Again, not too surprising as the data in the table before and after the update are the same. The problem comes in with updating the geometric. Say I want to remove the repeated point in geom2. So I do this update: update b_temp set geom2 = geom1; Doing a point count in node 1 shows the geom changed: select st_npoints(geom1), st_npoints(geom2) from b_temp; st_npoints | st_npoints ------------+------------ 4 | 4 Which is exactly what I expected. But if you look on node 2 (after slon is started) select st_npoints(geom1), st_npoints(geom2) from b_temp; st_npoints | st_npoints ------------+------------ 4 | 5 which is not what I expected. Looking into sl_log_1 I see: log_origin | log_xid | log_tableid | log_actionseq | log_cmdtype | log_cmddata ------------+----------+-------------+---------------+-------------+---------------------------------------------------------------- 1 | 82987244 | 217 | 55210696 | U | "msg_no"='11459815'where "msg_no"='11459815' and "rev_no"='0' Also, not what I expected. I believe the problem comes back to the PostGIS = operator that slony is using to compare the before and after data. Because the PostGIS = operator ignores directionality, these two geometrics are considered the same even though they are not. This causes issues where the data in my secondary node is different that the data in my primary node even though the two nodes are slon'd. Which, in my mind, is a huge issue. So, am I missing something? Is there some way to get slony to use The PostGIS function st_orderingequals() rather than = or st_equals()? Or is there some way to get slony to do a binary bit comparison of the two geometrics? if it helps, this is the slony trigger on the table in the master database: _ks_slony_logtrigger_217 AFTER INSERT OR DELETE OR UPDATE ON b_temp FOR EACH ROW EXECUTE PROCEDURE _ks_slony.logtrigger('_ks_slony', '217', 'kkv') Thanks for the long read.... - Brian _______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> Brian Peschel 2012-03-27T11:59:26 Moveset changes to sub_forward http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10659 <pre>Hi there We have 3 nodes in cluster. After moving a set from one node (node-1) to another (node-2), whats the best way to reset the origin in another subscriber (node-3) as it still talking to node-1 as node-1 is doing forward of node-2 changes to node-3 ; rather I want node-3 directly talk to node-2 (new origin) without sub_forward by node-1. The sl_subscribe looks like this: engine_db=# select * from sl_subscribe where sub_set=1;  sub_set | sub_provider | sub_receiver | sub_forward | sub_active ---------+--------------+--------------+-------------+------------        1 |            1 |            3 | f           | t        1 |            2 |            1 | t           | t (3 rows) Rather, after moveset, I expected, line 1 to go away and line-2 to have direct replication to 3 instead of forward through 1. Thanks for help Brian _______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> Brian Trudal 2012-03-19T21:04:36 Installing slony-2.1 in Windows Xp http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10651 <pre>Hello, We are Master students from Cologne University of Applied Sciences Germany. We are building a prototype for a biogas plant and we are having some problems implementing the structure We want do a Master-Slave replication between ubuntu(Master) and windows(Slave) in PostgreSQL 9.1 using Slony2.1. we have problems in installing slony 2.1 in windows. We have downloaded the source files. unlike previous versions slony 2.1 doesn't have a .exe file. So can you help us with the steps to install slony 2.1 in windows xp. We are looking forward for your support. Thanks &amp; Regards Esli _______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> ESLI george 2012-03-19T12:04:04 Slony installation query. http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10646 <pre>Hello, We are Master students from Cologne University of Applied Sciences Germany. We are building a prototype for a biogas plant and we are having some problems implementing the structure We want do a Master-Slave replication between ubuntu(Master) and windows(Slave) in PostgreSQL 9.1 using Slony2.1. we have problems in installing slony 2.1 in ubuntu. The problem is after configuring(./configure) and then compiling using command 'make' the file in slony1-2.1.1/src/backend/slony1_funcs.c. The header file Miscadmin.h is not found and most of the header files(nodes/makefuncs.h, etc.,) are not found. We have attached the screenshot of the error for Miscadmin.h. We need to know where we can find these header files and what is the problem in it. We are looking forward for your support. Thanks &amp; Regards Esli _______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> ESLI george 2012-03-16T15:34:06 Re copy currently replicated table http://comments.gmane.org/gmane.comp.db.postgresql.slony1.general/10644 <pre>Looks like a odd situation; I have 2 sets, and one set with 3 tables and another with 50+ tables. Both the sets are replicated to two subscribers; one set has correct data, but second set two tables are off. And both the subscribers are up2date with origin; but 2 tables out of 3, has wrong number of rows (way off) in subscriber-1; So, whats the best way to re-copy or re-initiate these two tables copy only to subsriber-1 without subsriber-2 (it shares the set) as subscriber-2 is prod read facing. Thanks for the help Brian _______________________________________________ Slony1-general mailing list Slony1-general-8kkgcvHRObyz5F2/bZa4Fw&lt; at &gt;public.gmane.org http://lists.slony.info/mailman/listinfo/slony1-general </pre> Brian Trudal 2012-03-16T01:52:22 Search Engine Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.db.postgresql.slony1.general