Dave Cramer | 22 Jul 20:53 2014
Picon

replicating from 9.3 to 8.4

Are there any known issues ?

Dave Cramer
_______________________________________________
Slony1-general mailing list
Slony1-general@...
http://lists.slony.info/mailman/listinfo/slony1-general
Ger Timmens | 17 Jul 23:45 2014

slony 2.2.3 experiences

Hi all,

After upgrading our environment from slony 2.1.4 to slony 2.2.3
we see 'a lot' more slony connections both on master, forwarders
as subscribers.

E.g. on the master we see approx 120 more 'idle' slony connections.
This connections start around 50, groing to 120 over time
(restarting slons, will bring it down and connections will increase again).

This is probably related to the changed failover logic in slony 2.2.x
over 2.1.x where each forwarding note should know about each
other node ?

If so, is there a way to go back to the 2.1.x behaviour (is it
configurable) ?

Thanks,

Ger Timmens
Dave Cramer | 16 Jul 18:24 2014
Picon

How to get database profiling with slony

I'm looking to figure out the read/write/transactions per day net of slony.

Log grepping is not an option as the app generates too many logs

Any ideas ?

Dave Cramer
_______________________________________________
Slony1-general mailing list
Slony1-general@...
http://lists.slony.info/mailman/listinfo/slony1-general
Dave Cramer | 14 Jul 15:16 2014
Picon

Slony over very long distances


How well does this work. Does anyone have some real world experience with this ?


Dave Cramer
_______________________________________________
Slony1-general mailing list
Slony1-general@...
http://lists.slony.info/mailman/listinfo/slony1-general
Steve Singer | 8 Jul 03:54 2014

Slony 2.2.3 released

The Slony team is pleased to announce Slony 2.2.3 the next minor release 
of the Slony 2.2.x series

Slony 2.2.3 includes the following changes

  - Bug 338 - Have ddlScript return a bigint instead of a integer
  - fixing  Deadlock with application during minor version slony upgrade
  - Bug 342 FAILOVER fixes for some multi-node configurations
  - Remove HAVE_POSIX_SIGNALS from config.h
  - Bug 344 Do not abort reading slon config values when an unrecognized 
one is encountered

Slony 2.2.3 can be downloaded from from the following URL

http://main.slony.info/downloads/2.2/source/slony1-2.2.3.tar.bz2
Dave Cramer | 27 Jun 22:04 2014
Picon

sl_log_x very large due to lagging subscription

If I drop the subscription through drop set will the log file be automagically cleaned up ?

If not how can I fix it ?

Dave Cramer
_______________________________________________
Slony1-general mailing list
Slony1-general@...
http://lists.slony.info/mailman/listinfo/slony1-general
Soni M | 25 Jun 17:00 2014
Picon

manually delete sl_log_x table

Hello everyone,

Is it OK to delete event log that has been replicated in sl_log_x.

Here's the function I created :

CREATE OR REPLACE FUNCTION _slony_example.delete_sl_log()
 RETURNS void
 LANGUAGE plpgsql
AS $function$
DECLARE
        v_origin        int8;
        v_seqno         int8;
        v_xmin          bigint;
BEGIN


                for v_origin, v_seqno, v_xmin in
                  select ev_origin, ev_seqno, "pg_catalog".txid_snapshot_xmin(ev_snapshot) from "_slony_example".sl_event
                  where (ev_origin, ev_seqno) in (select ev_origin, min(ev_seqno) from "_slony_example".sl_event where ev_type = 'SYNC' group by ev_origin)
                loop 

delete from _slony_example.sl_log_1 where log_origin = v_origin and log_txid < v_xmin;
delete from _slony_example.sl_log_2 where log_origin = v_origin and log_txid < v_xmin;
                end loop;

END;
$function$;

The Slony failed to switch sl_log for several hours, and event log keep accumulated in a table.

Will this action help to reduce slony lag that falls far behind ?

Thanks all.

--
Regards,

Soni Maula Harriz
_______________________________________________
Slony1-general mailing list
Slony1-general@...
http://lists.slony.info/mailman/listinfo/slony1-general
Dave Cramer | 18 Jun 21:59 2014
Picon

upgrading from 1.x to 2.x

What does this ominous message mean 

When Slony-I uninstalls itself, catalog corruptions are fixed back up.


Dave Cramer
_______________________________________________
Slony1-general mailing list
Slony1-general@...
http://lists.slony.info/mailman/listinfo/slony1-general
Tory M Blue | 11 Jun 00:45 2014
Picon

slony 2.1.3 run with postgresql 9.3.4?


I'm currently running 9.2.4 with slony 2.1.3.

I would like to use slony to upgrade my DB as i have for a few upgrades now, but want to make sure that 2.1.3 supports 9.3.x, as I usually upgrade postgres, then I upgrade slony.

I don't use pre-compiled binaries and I create a single rpm with postgres/slon built together.
So my steps are usually roll out the new rpm to my slaves, drop and add, they will then be getting data loaded as 9.3.4 wants it, but would still be running slony 2.1.3.  After my query slaves and switchover slave are updated this way, I switchover between my master (still running 9.2.4/2.1.3) and my slave (now running 9.3.4/2.1.3), and then I can drop add the old master and bring it to 9.3.4/2.1.3).

Thanks

Tory


_______________________________________________
Slony1-general mailing list
Slony1-general@...
http://lists.slony.info/mailman/listinfo/slony1-general
Venkata Balaji N | 10 May 02:04 2014
Picon

Slony Windows binaries for PostgreSQL-8.0

Hello,

Can anyone please help us know if it is possible to get the Slony installer binaries for Windows which are compatible with PostgreSQL-8.0.

This is critical for us and would highly appreciate any help in this regard.

Thanks & Regards,
VBN
_______________________________________________
Slony1-general mailing list
Slony1-general@...
http://lists.slony.info/mailman/listinfo/slony1-general
Glyn Astill | 1 May 18:39 2014
Picon

Re: Slony 2.2 failover changes


> From: Glyn Astill <glynastill@...>
>To: Steve Singer <ssinger@...>;
"slony1-general@..."
<slony1-general@...> 
>Sent: Thursday, 1 May 2014, 17:33
>Subject: Re: [Slony1-general] Slony 2.2 failover changes
> 
>
>
>----- Original Message -----
>
>> From: Steve Singer <ssinger@...>
>> Can you send me the slon logs for slon4 ? Ideally at debug level 4.
>> Also when the cluster is in this state: on node 4 do a
>> select * FROM _test_replication.sl_node;
>> 
>> and
>> 
>> select * FROM _test_replication.sl_listen where
>> li_origin=1, li_receiver=4;
>> 
>
>This time starting node 3 back up appears to not have let slonik move on from the failover, but now complete
because I'd inadvertently added in the drop node
command too.

Sorry, I'm on bad form today, that should read:

"This time starting node 3 back up appears to *have* let slonik move on from the failover, but not complete
because I'd inadvertently added in the drop node command too."

Gmane