Re: How is replication of TRIGGERS handled under Slony?

On Sun, Jun 26, 2011 at 5:29 AM, Steve Singer <ssinger_pg@...> wrote:
> If you tried to add a trigger to a slave without using EXECUTE SCRIPT (in
> 1.2) you might have corrupted your slave.

Yup, that's exactly what I did.  I ended up dropping the trigger on the master,
doing a complete data resync to the slave (re-created the replication set)
and then added the trigger again (using psql, not slony, just because I did not
know about SET ADD TRIGGER, thank you.)

> This is all different in 2.0,  I would recommend also looking at how 2.0
>  deals with this stuff and start planning an upgrade.

Yup, will do, thanks very much, Steve and Martijn!

Cheers,
-at

2.0.7 release schedule

Dear guys.

Do you know when SLONY-I 2.0.7 will be released?

I need bugfix(Bug #185) included in SLONY-I 2.0.7,
and I want to know the release schedule.

Thanking you in advance.

Re: 2.0.7 release schedule

On Mon, 11 Jul 2011, Akio Iwaasa wrote:

> Dear guys.
>
> Do you know when SLONY-I 2.0.7 will be released?
>
> I need bugfix(Bug #185) included in SLONY-I 2.0.7,
> and I want to know the release schedule.
>
> Thanking you in advance.

There have been a few other fixes since the last 2.0.7 release candidate.
I expect release another 2.0.7 release candidate in the next day or two.

If no one finds issues that RC then I expect us to do a final 2.0.7 in a 
week or two.

>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general@...
> http://lists.slony.info/mailman/listinfo/slony1-general
>

Re: 2.0.7 release schedule

On Mon, 2011-07-11 at 05:07 -0400, Steve Singer wrote:
> There have been a few other fixes since the last 2.0.7 release
> candidate.
> I expect release another 2.0.7 release candidate in the next day or
> two.
> 
> If no one finds issues that RC then I expect us to do a final 2.0.7 in
> a  week or two. 

RPM Buildfarm will be ready around Thursday. If you'd like me to test on
Fedora/RHEL, etc, may I ask you to postpone the release until then?

Regards,
--

-- 
Devrim GÜNDÜZ
Principal Systems Engineer  <at>  EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org  Twitter: http://twitter.com/devrimgunduz

_______________________________________________
Slony1-general mailing list
Slony1-general@...
http://lists.slony.info/mailman/listinfo/slony1-general

Re: 2.0.7 release schedule

Thanks Mr. Singer.
I'll testing RC and waiting for 2.0.7 release.

ssinger_pg@...さんの2011/07/11のメール
「Re: [Slony1-general] 2.0.7 release schedule」より。

>On Mon, 11 Jul 2011, Akio Iwaasa wrote:
>
>> Dear guys.
>>
>> Do you know when SLONY-I 2.0.7 will be released?
>>
>> I need bugfix(Bug #185) included in SLONY-I 2.0.7,
>> and I want to know the release schedule.
>>
>> Thanking you in advance.
>
>There have been a few other fixes since the last 2.0.7 release candidate.
>I expect release another 2.0.7 release candidate in the next day or two.
>
>If no one finds issues that RC then I expect us to do a final 2.0.7 in a 
>week or two.
>
>
>>
>> _______________________________________________
>> Slony1-general mailing list
>> Slony1-general@...
>> http://lists.slony.info/mailman/listinfo/slony1-general

Re: 2.0.7 release schedule

On 11-07-11 07:32 AM, Devrim GÜNDÜZ wrote:
> On Mon, 2011-07-11 at 05:07 -0400, Steve Singer wrote:
>> There have been a few other fixes since the last 2.0.7 release
>> candidate.
>> I expect release another 2.0.7 release candidate in the next day or
>> two.
>>
>> If no one finds issues that RC then I expect us to do a final 2.0.7 in
>> a  week or two.
>
> RPM Buildfarm will be ready around Thursday. If you'd like me to test on
> Fedora/RHEL, etc, may I ask you to postpone the release until then?
>

My thinking is that I'll try to get the next release candidate out 
before Thursday so you can test that on the RPM buildfarm and then I'll 
let you test that on the buildfarm before we do a final 2.0.7.  The next 
RC should address the pgport dependency issues a few people have been 
reporting on various Fedora/Redhat platforms.

I am also hoping to see another 2.1.0 beta is also expected soon.

> Regards,
>
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general <at> lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general

cluster slony multisite: master server dies, switching masters and slave rejoins late

  I work at a company where we have a cluster of 4 machines

with PG and Slony-I. These 4 machines are split in two data

centers, so we have one ´master´ and one ´slave´ on each data

center, and then one of the masters is the slave of the other:

   DC1        DC2

  Master --> Master

    |          |

    V          V

  Slave      Slave

  Our setup ensures that writes to the DB (which are done

only a few times a day by big batches with) are only done on

THE master (in the graph, the master in DC1).

  I have three questions about this setup:

  What happens if THE master dies? We can stop the batches

that inject the data, but will the slaves hold the reads

enable-thread-safety

_______________________________________________
Slony1-general mailing list
Slony1-general@...
http://lists.slony.info/mailman/listinfo/slony1-general

Re: enable-thread-safety

On 11-07-11 05:22 PM, Sam Nelson wrote:
> We're trying to upgrade a Slony instance from 1.2.x to 2.0.6 on a
> postgres 8.3.11 instance and in the process of configuring the new slony
> install, the configure script errors out saying that thread safety isn't
> enabled.
>

Verify which libpq slony/configure if finding.

If you have libpq installed somewhere without thread-safety it is 
possible that configure if finding that one instead of the one you compiled.

> I went and re-configured postgres, using the --enable-thread-safety
> flag, then ran make and make install.  I then restarted the postgres
> instance with pg_ctl -D <dir> restart -m fast.  The slony config script
> still complained about thready safety not being enabled
>
> My questions:
>
>    1. Should this have worked?
>          1. If not, which steps did I miss?  Re-initializing the cluster?
>    2. Does anyone know whether or not the RPMs and other various
>       binaries are compiled with thread safety enabled?
>
> ---
> ===========================
> Samuel Nelson
> Consistent State
> www.consistentstate.com <http://www.consistentstate.com>
> 303-955-0509
> ===========================
>
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general@...
> http://lists.slony.info/mailman/listinfo/slony1-general

Re: enable-thread-safety

_______________________________________________
Slony1-general mailing list
Slony1-general@...
http://lists.slony.info/mailman/listinfo/slony1-general