Is there a script somewhere to provide a report of what slony is attempting
to do ? In other words denormalize the slony config ?

Dave Cramer


On 19 June 2014 15:08, Steve Singer <ssinger at ca.afilias.info> wrote:

> On 06/19/2014 02:58 PM, Dave Cramer wrote:
>
>> Thanks Jan,
>>
>> I see if I squint and tilt my head a certain way that it reads correctly.
>>
>> Is there a debian 2.x package for wheezy ?
>>
>> Dave
>>
>>
> I think apt.postgresql.org has slony 2.2.x packages
>
> deb http://apt.postgresql.org/pub/repos/apt/ wheezy-pgdg main
>
>  Dave Cramer
>>
>>
>> On 18 June 2014 18:08, Jan Wieck <jan at wi3ck.info
>> <mailto:jan at wi3ck.info>> wrote:
>>
>>     On 06/18/14 15:59, Dave Cramer wrote:
>>
>>         What does this ominous message mean
>>
>>         When Slony-I uninstalls itself, catalog corruptions are fixed
>>         back up.
>>
>>
>>     Slony 1.x was designed to run on PostgreSQL versions prior to 8.3.
>>     Since the "session_replication_role" and trigger configuration
>>     features were new in 8.3, Slony 1.x disabled triggers and rewrite
>>     rules by hacking pg_class on replicas. When you use UNINSTALL NODE,
>>     those hacks are reverted and you end up with a clean system catalog
>>     again on that replica.
>>
>>
>>     Jan
>>
>>     --
>>     Jan Wieck
>>     Senior Software Engineer
>>     http://slony.info
>>
>>
>>
>>
>> _______________________________________________
>> Slony1-general mailing list
>> Slony1-general at lists.slony.info
>> http://lists.slony.info/mailman/listinfo/slony1-general
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20140626/04ae891c/attachment.htm