Tue Jun 14 21:04:48 PDT 2005
- Previous message: [Slony1-commit] By cbbrowne: Added a couple of paragraphs to better explain the
- Next message: [Slony1-commit] By cbbrowne: A number of formatting changes...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message: ----------- Added recommendation that people consider upgrading to PG 7.4.8 as it resolves race conditions that Slony-I exposed. Modified Files: -------------- slony1-engine/doc/adminguide: faq.sgml (r1.37 -> r1.38) -------------- next part -------------- Index: faq.sgml =================================================================== RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/faq.sgml,v retrieving revision 1.37 retrieving revision 1.38 diff -Ldoc/adminguide/faq.sgml -Ldoc/adminguide/faq.sgml -u -w -r1.37 -r1.38 --- doc/adminguide/faq.sgml +++ doc/adminguide/faq.sgml @@ -732,8 +732,12 @@ <para> On at least one occasion, this has resolved the problem, so it is worth trying this.</para> -<para> It appears increasingly likely that this problem represents a -&postgres; bug as opposed to one in &slony1;.</para> +<para> This problem represents a &postgres; bug as opposed to one in +&slony1;. Version 7.4.8 was released with two resolutions to race +conditions that should resolve the issue. Thus, if you are running a +version of &postgres; earlier than 7.4.8, you should consider +upgrading to resolve this. +</para> </answer> </qandaentry>
- Previous message: [Slony1-commit] By cbbrowne: Added a couple of paragraphs to better explain the
- Next message: [Slony1-commit] By cbbrowne: A number of formatting changes...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list