Tue May 25 06:30:02 PDT 2010
- Previous message: [Slony1-hackers] [Slony1-bugs] Slony triggers included in pg_dump
- Next message: [Slony1-hackers] [Slony1-general] [Slony1-bugs] Slony triggers included in pg_dump
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gurjeet Singh wrote: > 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> > > Documentation patch applied. > 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 > > > ------------------------------------------------------------------------ > > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general -- Steve Singer Afilias Canada Data Services Developer 416-673-1142
- Previous message: [Slony1-hackers] [Slony1-bugs] Slony triggers included in pg_dump
- Next message: [Slony1-hackers] [Slony1-general] [Slony1-bugs] Slony triggers included in pg_dump
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-hackers mailing list