Thread: Re: [GENERAL] Slony-I 1.0.4 Released
Sorry folks, the Slony-I team has produced a great product, but the project management (that's mostly me here) sucks big time! Shortly after giving Chris Browne green light for the 1.0.4 announcement we found a way to guard against bug #896. That being a really bad one I decided to stop the 1.0.4 release and go for 1.0.5 including that fix. But I failed to make sure Chris, Justin and others involved in the announcement process get the message. I have just committed those changes and 1.0.5 should be available later today. I apologize for the confusion and look forward to retire from the Slony-I project leadership position in order to fully focus on the multimaster replication project Afilias has decided to put forward. Jan On 10/21/2004 5:55 PM, Chris Browne wrote: > The Slony-I team is proud to present the 1.0.4 release of the most > advanced replication solution for the most advanced Open Source > Database in the world. > > The release tarball is available for download > http://developer.postgresql.org/~wieck/slony1/download/slony1-1.0.4.tar.gz > > There are a limited number of "new features" this release largely in > terms of adding in the ability to move or drop tables and sequences > from replication: > > - SET DROP TABLE - drops a table from replication > - SET DROP SEQUENCE - does the same for sequences > - SET MOVE TABLE - moves a table from one replication set to another > - SET MOVE SEQUENCE - moves a sequence from one replication set to another > > Other changes involve smoothing out the 'sharp edges' found by early > adopters, notably including: > > - Frequently vacuuming pg_listener; growth of dead tuples could hurt > performance > > - A cleanup process for pg_listener resolves cases where old slon > processes may have terminated due to network problems, leaving > backends around holding onto event notifications > > - Lowered lock level on sl_event, resolving issues where pg_dump > would block Slony-I > > - Purges CONFIRM entries for nodes that don't exist anymore > > - Substantially increased documentation > > - More sophisticated administration scripts > > - Now uses string comparison for user defined types that do not have > a suitable comparison operation > > - Safer log purging > > - Various other bug fixes and "improved cleanliness." > > - As of 1.0.4, the slon replication engine refuses to work against > any database that does not have the stored procedures for the same > version loaded or where the shared object containing the C language > support functions and the log trigger does not match the version > number. in a cluster must be upgraded at once. > > See the HISTORY-1.0 file for a detailed list of changes. > > <http://slony.info/> -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #
On 10/22/2004 11:29 AM, Ed L. wrote: > Wow. First, thanks again for all your efforts, Jan. Second, I'm > disappointed to hear the slony author and lead developer is leaving the > slony leadership. When is that going to happen? And what does that mean > with respect to your future involvement in slony? It means that I will try to do with Slony-I what I have done successfully with several other PostgreSQL related projects - to make sure the project doesn't depend on me in person any more. None of the big items I've done (rewrite rule system, PL/pgSQL, PL/Tcl, TOAST, NUMERIC, foreign keys) really requires my attention if there's a bug. I was able to do the conceptual work and important parts of the implementation, but I didn't get stuck in/with the maintenance. I constider this a very important aspect of being a CORE developer. What I am trying to do is to spend less and less time on Slony-I and more and more time on Slony-II - the synchronous multi-master system. Slony-I was for sure one of the better things that I've done so far, but it's not going to allow early retirement with financial independance and wealth. And as long as Afilias is using Slony-I in production, Andrew Sullivan will not let me do whatever I want if there's a severe problem nobody else can fix. So don't worry, I'll be around. Jan > > Ed > > > On Friday October 22 2004 7:26, Jan Wieck wrote: >> Sorry folks, >> >> the Slony-I team has produced a great product, but the project >> management (that's mostly me here) sucks big time! >> >> Shortly after giving Chris Browne green light for the 1.0.4 announcement >> we found a way to guard against bug #896. That being a really bad one I >> decided to stop the 1.0.4 release and go for 1.0.5 including that fix. >> But I failed to make sure Chris, Justin and others involved in the >> announcement process get the message. >> >> I have just committed those changes and 1.0.5 should be available later >> today. >> >> I apologize for the confusion and look forward to retire from the >> Slony-I project leadership position in order to fully focus on the >> multimaster replication project Afilias has decided to put forward. >> >> >> Jan >> >> On 10/21/2004 5:55 PM, Chris Browne wrote: >> > The Slony-I team is proud to present the 1.0.4 release of the most >> > advanced replication solution for the most advanced Open Source >> > Database in the world. >> > >> > The release tarball is available for download >> > >> > http://developer.postgresql.org/~wieck/slony1/download/slony1-1.0.4.tar >> >.gz >> > >> > There are a limited number of "new features" this release largely in >> > terms of adding in the ability to move or drop tables and sequences >> > from replication: >> > >> > - SET DROP TABLE - drops a table from replication >> > - SET DROP SEQUENCE - does the same for sequences >> > - SET MOVE TABLE - moves a table from one replication set to another >> > - SET MOVE SEQUENCE - moves a sequence from one replication set to >> > another >> > >> > Other changes involve smoothing out the 'sharp edges' found by early >> > adopters, notably including: >> > >> > - Frequently vacuuming pg_listener; growth of dead tuples could hurt >> > performance >> > >> > - A cleanup process for pg_listener resolves cases where old slon >> > processes may have terminated due to network problems, leaving >> > backends around holding onto event notifications >> > >> > - Lowered lock level on sl_event, resolving issues where pg_dump >> > would block Slony-I >> > >> > - Purges CONFIRM entries for nodes that don't exist anymore >> > >> > - Substantially increased documentation >> > >> > - More sophisticated administration scripts >> > >> > - Now uses string comparison for user defined types that do not have >> > a suitable comparison operation >> > >> > - Safer log purging >> > >> > - Various other bug fixes and "improved cleanliness." >> > >> > - As of 1.0.4, the slon replication engine refuses to work against >> > any database that does not have the stored procedures for the same >> > version loaded or where the shared object containing the C language >> > support functions and the log trigger does not match the version >> > number. in a cluster must be upgraded at once. >> > >> > See the HISTORY-1.0 file for a detailed list of changes. >> > >> > <http://slony.info/> -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #
Wow. First, thanks again for all your efforts, Jan. Second, I'm disappointed to hear the slony author and lead developer is leaving the slony leadership. When is that going to happen? And what does that mean with respect to your future involvement in slony? Ed On Friday October 22 2004 7:26, Jan Wieck wrote: > Sorry folks, > > the Slony-I team has produced a great product, but the project > management (that's mostly me here) sucks big time! > > Shortly after giving Chris Browne green light for the 1.0.4 announcement > we found a way to guard against bug #896. That being a really bad one I > decided to stop the 1.0.4 release and go for 1.0.5 including that fix. > But I failed to make sure Chris, Justin and others involved in the > announcement process get the message. > > I have just committed those changes and 1.0.5 should be available later > today. > > I apologize for the confusion and look forward to retire from the > Slony-I project leadership position in order to fully focus on the > multimaster replication project Afilias has decided to put forward. > > > Jan > > On 10/21/2004 5:55 PM, Chris Browne wrote: > > The Slony-I team is proud to present the 1.0.4 release of the most > > advanced replication solution for the most advanced Open Source > > Database in the world. > > > > The release tarball is available for download > > > > http://developer.postgresql.org/~wieck/slony1/download/slony1-1.0.4.tar > >.gz > > > > There are a limited number of "new features" this release largely in > > terms of adding in the ability to move or drop tables and sequences > > from replication: > > > > - SET DROP TABLE - drops a table from replication > > - SET DROP SEQUENCE - does the same for sequences > > - SET MOVE TABLE - moves a table from one replication set to another > > - SET MOVE SEQUENCE - moves a sequence from one replication set to > > another > > > > Other changes involve smoothing out the 'sharp edges' found by early > > adopters, notably including: > > > > - Frequently vacuuming pg_listener; growth of dead tuples could hurt > > performance > > > > - A cleanup process for pg_listener resolves cases where old slon > > processes may have terminated due to network problems, leaving > > backends around holding onto event notifications > > > > - Lowered lock level on sl_event, resolving issues where pg_dump > > would block Slony-I > > > > - Purges CONFIRM entries for nodes that don't exist anymore > > > > - Substantially increased documentation > > > > - More sophisticated administration scripts > > > > - Now uses string comparison for user defined types that do not have > > a suitable comparison operation > > > > - Safer log purging > > > > - Various other bug fixes and "improved cleanliness." > > > > - As of 1.0.4, the slon replication engine refuses to work against > > any database that does not have the stored procedures for the same > > version loaded or where the shared object containing the C language > > support functions and the log trigger does not match the version > > number. in a cluster must be upgraded at once. > > > > See the HISTORY-1.0 file for a detailed list of changes. > > > > <http://slony.info/>
pgsql@bluepolka.net ("Ed L.") wrote:
> Wow. First, thanks again for all your efforts, Jan. Second, I'm
> disappointed to hear the slony author and lead developer is leaving
> the slony leadership. When is that going to happen? And what does
> that mean with respect to your future involvement in slony?
In some respects, it's a healthy thing for there to be _some_ change
that takes place. A project that is comprised of one person can
pretty easily disappear if that one person steps away. Furthermore,
one of the purported merits of open source is that it benefits from
diverse involvement. A healthy OSS project sees changes coming in
from _multiple_ people; from the diversity of people comes a diversity
in points of view and in ideas of what can be added. That has already
been the case with Slony-I.
Furthermore, I don't see this leading to Jan "disappearing from Slony"
at all. As one who 'groks the code well,' his wisdom will doubtless
be drawn upon. (And since those paying his salary depend quite a lot
on Slony-I, there's a certain amount of influence that could be
brought to bear ;-).) He's trying to spend some time concentrating on
yet another project that is also called Slony, namely Slony-II.
The point of Slony-I was to provide an efficient way to bring a bunch
of nodes into sync. Slony-II is to extend that further to support
multimaster replication. It needs to start with databases that are in
sync, ergo requiring starting with Slony-I. Others of us may be doing
most of the "heavy lifting" to finish off features already
contemplated for Slony-I, but I seriously doubt that means Jan will be
completely uninvolved.
There needs to be an interface between the phases, too. After all,
there has to be some transformation to take a set of "Slony-I
replicated" systems to then take them into "Slony-II mode." I'll bet
that means that Slony-I will have to add some code to become
"Slony-II-aware"...
--
output = ("cbbrowne" "@" "acm.org")
http://www.ntlug.org/~cbbrowne/
"Markets can remain irrational longer than you can remain solvent."
-- J. M. Keynes