Re: [Slony1-general] problems with slony1-1.2.10 and postgresql-8.2.4

On Wed, 1 Aug 2007, David Rees wrote: On 8/1/07, Jeff Frost [EMAIL PROTECTED] wrote: stdin:17: PGRES_FATAL_ERROR load '$libdir/xxid'; - ERROR: incompatible library /usr/lib64/pgsql/xxid.so: missing magic block Except, I don't know why it's looking in /usr/lib64/pgsql because this is a 32 bit

Re: [Slony1-general] problems with slony1-1.2.10 and postgresql-8.2.4

On Wed, 1 Aug 2007, David Rees wrote: On 8/1/07, Jeff Frost [EMAIL PROTECTED] wrote: When I upgrade I put Postgres / Slony into a unique directory for each build (for example /usr/local/pgsql-8.2.4-2007080101 and /usr/local/slony-1.2.10-2007080101) and then symlink that folder to the same

Re: [Slony1-general] problems with slony1-1.2.10 and postgresql-8.2.4

On Mon, 6 Aug 2007, Jeff Frost wrote: [EMAIL PROTECTED] ~]# rpm -q --queryformat=%{ARCH} postgresql-server x86_64 [EMAIL PROTECTED] ~]# file `rpm -ql postgresql-server|grep /usr/bin` /usr/bin/initdb: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared

Re: [Slony1-general] bug in deadlock handling?

On Tue, 18 Sep 2007, Jeff Frost wrote: Hi guys, I've got an interesting situation on a slony 1.2.10 3 node cluster. Both slaves get their data direct from the master. Everything has been running well up to a few days ago. Now every time we try to add a new table to the cluster, we end up

Re: [Slony1-general] bug in deadlock handling?

was supposed to be slony aware? -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954___ Slony1-general mailing list Slony1-general@lists.slony.info http

Re: [Slony1-general] bug in deadlock handling?

On Wed, 19 Sep 2007, Jeff Frost wrote: On Wed, 19 Sep 2007, Christopher Browne wrote: Bails out is the wrong description. Clobbered by the pgsql deadlock detection system, leaving the cluster in an unstable state would be more accurate, if that's what happened. I don't know that there's

[Slony1-general] can you change a node's id?

master? -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954 ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo

Re: [Slony1-general] can you change a node's id?

scripts after the upgrade. -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954 ___ Slony1-general mailing list Slony1-general@lists.slony.info http

Re: [Slony1-general] Bad failure mode encountered during EXECUTE SC RIPT(maybe fixed in 1.2.12?)

Casey, if you search through the archives for deadlock you'll find a similar problem I had. This has been fixed in 1.2.12. Sorry for top posting, my phone doesn't quote worth a flip. --- Original Message --- From: Casey Duncan [EMAIL PROTECTED] To: slony1-general@lists.slony.info

Re: [Slony1-general] table_id error??

clustername is testcluster, then: select * from _testcluster.sl_table where tab_id = 2; -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954 ___ Slony1-general

Re: [Slony1-general] Slony with Fedora Unbuntu

version is the same, it will work. Can anyone confirm this? It will work. The PostgreSQL versions do not need to be the same. You could couple this with an upgrade to 8.2.7 or even 8.3.1 if you like. -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http

Re: [Slony1-general] Version mismatch? It's a new system...

it was installed. BTW, if this is a brand new server, why not start with postgresql 8.3.1 instead of 8.3.0? -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954

Re: [Slony1-general] Version mismatch? It's a new system...

: 1.2.13 != Slony-I version in PG build 1.2.9 stdin:5: ERROR: no admin conninfo for node 0 -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954 ___ Slony1-general

Re: [Slony1-general] slon can't distinguish nodes?

figure out which node number it is working on? There doesn't seem to be any way to tell it. It calls the getlocalnodeid(name) function on the DB specified in the conninfo when it's started. How are you providing the conninfo to the slon daemons? -- Jeff Frost, Owner [EMAIL PROTECTED

Re: [Slony1-general] slon can't distinguish nodes?

On Wed, 2 Apr 2008, Craig James wrote: Jeff Frost wrote: On Wed, 2 Apr 2008, Craig James wrote: I keep getting this error: remoteListenThread_1: db_getLocalNodeId() returned 2 - wrong database? I suspect the slon daemon can't handle port numbers correctly. In this case, both the master

RE: [Slony1-general] slon can't distinguish nodes?

and better yet, can you connect to both of them on the machine where the slons will run like this: psql -h au -p 5433 -U postgres my_db psql -h au -p 5432 -U postgres my_db and if so, what's the output of: select _my_db_cluster.getlocalnodeid('_my_db_cluster'); on both

RE: [Slony1-general] slon can't distinguish nodes?

On the master, something is odd: my_db=# select * from _my_db_cluster.sl_path; pa_server | pa_client |pa_conninfo | pa_connretry ---+---+--+--- --- 2 | 1 | dbname=my_db host=au

Re: [Slony1-general] Postgresql upgrades and Slony

. The answer is unfortunately, still no. So, your upgraded server will become node 3 and if that's going to be the new master and you want it to be node 1, the only way to do this is tear down replication and reinstall the cluster with different node IDs. -- Jeff Frost, Owner [EMAIL

Re: [Slony1-general] Postgresql upgrades and Slony

of ORIGIN NODE instead of 1? I think this plus the ability to DEFINE aliases would take care of all these issues. Perhaps we should make the DEFINE more prominent in the docs. I suppose also making EVENT NODE required instead of optional could help with that as well. -- Jeff Frost, Owner

Re: [Slony1-general] Postgresql upgrades and Slony

On Wed, 9 Apr 2008, Christopher Browne wrote: Vivek Khera [EMAIL PROTECTED] writes: On Apr 8, 2008, at 4:29 PM, Jeff Frost wrote: I think if the default event node wasn't always 1, but in fact the current master, then things would be less painful when you end up with a master that isn't node

[Slony1-general] 1.2.14rc -= 1.2.14?

Is 1.2.14rc going to get promoted to 1.2.14 anytime soon or is there another rc forthcoming? I've been using it in a few 8.3.1 environments with no problems. -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX

[Slony1-general] typo in configure-replication.txt

This is the first script to run; it sets up the requested nodes as being Slony-I nodes, adding in some Slony-I-specific config tables and such. -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954

Re: [Slony1-general] Version 1.2.14 available

/include/pgsql/server/ checking for correct version of PostgreSQL... 8.3 pg_config says pg_sharedir is /usr/share/pgsql/ so that seems fine. -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954

Re: [Slony1-general] after I initialize a set, can I add other table to it again?

, subscribe the set to the same nodes as the original set, then merge the set. See the 12.1. Adding a table to replication section of the docs here: http://www.slony.info/documentation/addthings.html -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com

[Slony1-general] slony and autovacuum

Is it no longer recommended to disable autovacuum for the slony tables? -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 916-647-6411 FAX: 916-405-4032 ___ Slony1-general mailing list Slony1

Re: [Slony1-general] Instructions for setup of slony pair

schema. For instance if your cluster is called mycluster, then you would: DROP SCHEMA _mycluster CASCADE; to drop it. You have to do that on all nodes before starting over again. -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 916

Re: [Slony1-general] Instructions for setup of slony pair

: DROP SCHEMA _mycluster CASCADE; to drop it. You have to do that on all nodes before starting over again. DK: This is from psql, not slonik, right? JF: That's correct. -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 916-647

Re: [Slony1-general] what changes require the use of execute_script

tables. Check out the documentation here: http://slony.info/documentation/ddlchanges.html Especially the section: 15.1. Changes that you might not want to process using EXECUTE SCRIPT -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 916

Re: [Slony1-general] truncate failed???

. From the docs: TRUNCATE cannot be used on a table that has foreign-key references from other tables, unless all such tables are also truncated in the same command. Checking validity in such cases would require table scans, and the whole point is not to do one. -- Jeff Frost, Owner

Re: [Slony1-general] 32 BIT vs 64 BIT architecture

, this will work fine with Slony1. You can also use a different version of postgres on the various nodes allowing an upgrade path that provides less downtime than the traditional dump/restore method. -- Jeff Frost, Owner [EMAIL PROTECTED] Frost Consulting, LLC http

Re: [Slony1-general] slony rep error on start up: Slony-I: setAddTable_int():

; GRANT SELECT ON TABLE chart_data TO mesview; -- Jeff Frost, Owner j...@frostconsultingllc.com Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 916-647-6411 FAX: 916-405-4032 ___ Slony1-general mailing list Slony1-general

Re: [Slony1-general] Initial replication of sequences is failing

Jeff Frost wrote: Andrew Sullivan wrote: On Tue, Jun 02, 2009 at 10:30:45AM -0500, Sean Staats wrote: I created a new replication cluster. It turns out that starting the table IDs at id=1 and the sequence IDs at id=1001 didn't make any difference as slony gave me the same error

Re: [Slony1-general] Initial replication of sequences is failing

Sean Staats wrote: Nope. There is no firewall between the servers. Andrew Sullivan wrote: On Tue, Jun 02, 2009 at 01:17:19PM -0700, Jeff Frost wrote: The DB in question is 144GB and it's being replicated over a relatively slow link. It seems to do about 1GB/hr, but never gets past

[Slony1-general] 2.0.1 log volume

? Log settings: log_level = 1 syslog = 2 -- Jeff Frost, Owner j...@frostconsultingllc.com Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 916-647-6411 FAX: 916-405-4032 ___ Slony1-general mailing list Slony1-general

Re: [Slony1-general] 2.0.1 log volume

Devrim GÜNDÜZ wrote: On Tue, 2009-07-28 at 14:49 -0700, Jeff Frost wrote: Any way I can get it to quiet down? IIRC you will need to lower DEBUGLEVEL, which is in slon_tools.conf. And that's different from log_level in slon.conf? Here's the comment from the sample: # Debug log

Re: [Slony1-general] 2.0.1 log volume

Christopher Browne wrote: Jeff Frost j...@frostconsultingllc.com writes: And that's different from log_level in slon.conf? Here's the comment from the sample: # Debug log level (higher value == more output). Range: [0,4], default

Re: [Slony1-general] More on 8.4 .vs. Slony 2.0.2

? DROP NODE doesn't do an UNINSTALL NODE. What does psql show for '\d banned_ip' in the node 4 DB? -- Jeff Frost j...@pgexperts.com COO, PostgreSQL Experts, Inc. Phone: 1-888-PG-EXPRT x506 http://www.pgexperts.com/ ___ Slony1-general mailing list

Re: [Slony1-general] Still can't checkout Slony1-www repository

is not used anymore ? If this is a problem, what can i do to help ? Looks like you forgot to cvs login. Just do it like so: CVSROOT=:pserver:anonym...@main.slony.info:/slony1 cvs login CVSROOT=:pserver:anonym...@main.slony.info:/slony1 cvs co slony1-engine -- Jeff Frost j

Re: [Slony1-general] Still can't checkout Slony1-www repository

damien clochard wrote: Jeff Frost a écrit : damien clochard wrote: Hi ! As i said 6 months ago, it is impossible to checkout the slony's website CVS : $ export CVSROOT=:pserver:anonym...@main.slony.info:/slony1 $ cvs co slony1-www/ cvs checkout: Updating slony1-www cvs

Re: [Slony1-general] Ugh - New Issue with using Slony to upgrade Postgresql

switching the ports. But, if you forget to do it in the future, you can fix it afterwards by going bare metal and updating the paths in the _tickerform.sl_path table on the nodes that don't have the correct information. -- Jeff Frost j...@pgexperts.com COO, PostgreSQL Experts, Inc. Phone: 1-888-PG

Re: [Slony1-general] Ugh - New Issue with using Slony to upgrade Postgresql

information. -- Jeff Frost j...@pgexperts.com COO, PostgreSQL Experts, Inc. Phone: 1-888-PG-EXPRT x506 http://www.pgexperts.com/ ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general

Re: [Slony1-general] Ugh - New Issue with using Slony to upgrade Postgresql

Karl Denninger wrote: Jeff Frost wrote: Karl Denninger wrote: But they should have switched the master to Node #4 when the move set command was executed. When they reconnect they should be doing so to Node #2, not Node #2 - IF they saw the move set command (and it appears they did

Re: [Slony1-general] How do you rejoin a dropped nodes?

reports no_id -1 WHY??? what's wrong with it? I already inform all the node that I had dropped the Node1, why it said Error: ev_origin for store_node cannot be the new node -- Jeff Frost j...@pgexperts.com COO, PostgreSQL Experts, Inc. Phone: 1-888-PG-EXPRT x506 http

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

Would you consider slony1-2.0.4 as ready for production use? i recall a thread from December indicating that 2.0.3 was not ready for production use. --- Jeff Frost j...@pgexperts.com CTO, PostgreSQL Experts, Inc. Phone: 1-888-PG-EXPRT x506 FAX: 415-762-5122 http://www.pgexperts.com

Re: [Slony1-general] Install without root permissions

Ah yes, the issue is that you need a few .so files installed in the postgresql libdir. that appears to be: /usr/lib64/pgsql on your installation. BTW, any chance you could subscribe to the mailing list so we don't have to keep moderating each one of your emails to the list? On Mar 4, 2012,

[Slony1-general] slony upstart script for Ubuntu 10.04+

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 -- Jeff Frost j...@pgexperts.com CTO, PostgreSQL Experts, Inc. Phone: 1

Re: [Slony1-general] slony upstart script for Ubuntu 10.04+

On May 16, 2012, at 7:46 AM, Stuart Bishop wrote: On Wed, May 16, 2012 at 8:34 PM, Steve Singer ssin...@ca.afilias.info wrote: On 12-05-15 05:52 PM, Jeff Frost wrote: I wrote an upstart script for starting slony on ubuntu 10.04+. If there's any interest in including it in the slony distro

[Slony1-general] Bug 255 for 2.0.x branch and 2.1.1 status

Looks like a fix for bug 255 was committed to the 2.0 branch, but there's not been a release yet which incorporates it. Is that correct? If so, is there an estimate on when that will be released? Also, what's the current status of 2.1.1? Considered ready for production use? -- Jeff Frost j

Re: [Slony1-general] Slony replication has stopped replicating

. ___ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general --- Jeff Frost j...@pgexperts.com CTO, PostgreSQL Experts, Inc. Phone: 1-888-PG-EXPRT x506 FAX: 415-762-5122 http://www.pgexperts.com

[Slony1-general] subscriber node has wrong localnodeid after initial sync

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

Re: [Slony1-general] Still having issues with wide area replication. large table , copy set 2 failed

It's probably a firewall timing out your PostgreSQL connection while the indexes are being built on the replica. Look into tcp keep alive settings. On Feb 15, 2014, at 22:09, Tory M Blue tmb...@gmail.com wrote: So I've been fighting with this for a few months. I had someone on slony Dev

Re: [Slony1-general] Still having issues with wide area replication. large table , copy set 2 failed

On Feb 15, 2014, at 11:25 PM, Tory M Blue tmb...@gmail.com wrote: On Sat, Feb 15, 2014 at 10:48 PM, Jeff Frost j...@pgexperts.com wrote: It's probably a firewall timing out your PostgreSQL connection while the indexes are being built on the replica. Look into tcp keep alive settings

Re: [Slony1-general] subscriber node has wrong localnodeid after initial sync

| 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 j

Re: [Slony1-general] Still having issues with wide area replication. large table , copy set 2 failed

On Feb 16, 2014, at 5:00 PM, Tory M Blue tmb...@gmail.com wrote: As can be seen the connection is reaped, slon/postgres continue on their way, it's not until the next data copy is required that it finds it's connection is no longer there. Why it can't recreate a conneciton as one

Re: [Slony1-general] Still having issues with wide area replication. large table , copy set 2 failed

to the Moon too, but that's another story. Jan, is that only in 2.2+? I don't see the settings in the sample slon.conf before that version. -- Jeff Frost j...@pgexperts.com CTO, PostgreSQL Experts, Inc. Phone: 1-888-PG-EXPRT x506 FAX: 415-762-5122 http://www.pgexperts.com

[Slony1-general] help tuning to reduce replication lag

First, I have a question. The docs here: http://main.slony.info/documentation/2.1/deploymentconcerns.html#AEN2499 indicate that 0.978 seconds until close cursor means that processing took 0.978 seconds against the provider. Does that mean this is how long it took to iterate over the entire

Re: [Slony1-general] Fwd: help tuning to reduce replication lag

On Apr 2, 2014, at 1:28 PM, Christopher Browne cbbro...@afilias.info wrote: It's taking a thousand-ish seconds to process ~200K inserts/updates/deletes, which doesn't seem ludicrously out of line with what I'd expect. It doesn't seem likely to me that the amount of memory that you have is

Re: [Slony1-general] Fwd: help tuning to reduce replication lag

On Apr 2, 2014, at 2:14 PM, Christopher Browne cbbro...@afilias.info wrote: The disk hardware is pretty zippy and showing no signs of iowait, but it's definitely burning up the CPU and there's no way to thread that up to use more cores in current versions, right? Even if we split the

[Slony1-general] 2.1.4 can't update pg_class as superuser

Seeing this error from finishTableAfterCopy: PGRES_FATAL_ERROR ERROR: permission denied for relation pg_class CONTEXT: SQL statement update pg_catalog.pg_class set relhasindex ='t' where oid = i_oid slony 2.1.4 connecting to postgresql 9.2.9 as the slony user which is a postgresql

Re: [Slony1-general] 2.1.4 can't update pg_class as superuser

On Sep 30, 2014, at 5:03 PM, Greg Sabino Mullane g...@endpoint.com wrote: On Tue, Sep 30, 2014 at 03:18:42PM -0700, Jeff Frost wrote: Seeing this error from finishTableAfterCopy: PGRES_FATAL_ERROR ERROR: permission denied for relation pg_class slony 2.1.4 connecting to postgresql 9.2.9

Re: [Slony1-general] 2.1.4 can't update pg_class as superuser

On Sep 30, 2014, at 5:05 PM, Jeff Frost j...@pgexperts.com wrote: On Sep 30, 2014, at 5:03 PM, Greg Sabino Mullane g...@endpoint.com wrote: On Tue, Sep 30, 2014 at 03:18:42PM -0700, Jeff Frost wrote: Seeing this error from finishTableAfterCopy: PGRES_FATAL_ERROR ERROR: permission

Re: [Slony1-general] Lots of data in sl_log_? but sl_status shows lag of 0

On Jan 21, 2015, at 06:24, Dave Cramer davecra...@gmail.com wrote: How is this possible ? Cleanup hasn't run? Is the slon for the provider still running? Anything interesting in the log? ___ Slony1-general mailing list

Re: [Slony1-general] Slony Process Repeatedly Killed

> On Dec 23, 2015, at 7:16 PM, Grant Schaefer > wrote: > > Hello - > > I'm deploying Slony1-2.2.4 from a PG 9.2 instance to 9.4. All data within > subscribed tables is UTF8, the subscribed node contains a firewall so that > the slon daemon is not killed during

Re: [Slony1-general] Slony and streaming replication combo

I've done this. It works fine. Make sure you install the slony extensions on Old B and New B in the event you need to fail over to one of the B nodes. > On Feb 22, 2017, at 6:52 PM, Steve Singer wrote: > > I can't think why it wouldn't work. You should be able to do