On Tue, May 18, 2010 at 10:55 PM, Jan Wieck <JanWieck at yahoo.com> wrote:

> On 5/16/2010 8:22 AM, Gurjeet Singh wrote:
>
>> Hi All,
>>
>>    The docs here http://www.slony.info/documentation/triggers.html says
>> that post Postgres 8.3 version
>>
>> <snip>
>>
>>    * If you take a pg_dump of a Slony-I node, and drop out the Slony-I
>>      namespace, this now cleanly removes /all/ Slony-I components,
>>      leaving the database, /including its schema,/ in a "pristine",
>>      consistent fashion, ready for whatever use may be desired.
>> </snip>
>>
>> But I see that when dumping a schema containing tables monitored by Slony,
>> the dump still shows the log triggers on those tables.
>>
>
> I think you misinterpret the statement.
>
> If you take a complete dump of all schemas, restore that and THEN drop the
> slony schema, you have a pristine stand alone system as the result.
>
> pg_dump does not exclude cross-schema definitions like those triggers. You
> will get the same for example with foreign keys. For a table in the schema
> you are dumping, that references a table in a non-dumped schema, pg_dump
> will still emit the ALTER TABLE attempting to create the constraint.
>
>
Makes sense now. But I guess the statement should have read like this:

<snip>

   * If you restore a backup of a Slony-I node (taken by pg_dump or any
other method), and drop the Slony-I
     namespace, this now cleanly removes /all/ Slony-I components,
     leaving the database, /including its schema,/ in a "pristine",
     consistent fashion, ready for whatever use may be desired.
</snip>


Regards,

-- 
gurjeet.singh
@ EnterpriseDB - The Enterprise Postgres Company
http://www.enterprisedb.com

singh.gurjeet@{ gmail | yahoo }.com
Twitter/Skype: singh_gurjeet

Mail sent from my BlackLaptop device
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-hackers/attachments/20100524/90492445/attachment.htm