Mon May 17 11:20:07 PDT 2010
- Previous message: [Slony1-commit] slony1-engine/src/backend slony1_funcs.v83.sql slony1_funcs.v84.sql
- Next message: [Slony1-commit] slony1-engine/doc/adminguide triggers.sgml
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine/doc/adminguide
In directory main.slony.info:/tmp/cvs-serv6878/doc/adminguide
Modified Files:
Tag: REL_2_0_STABLE
triggers.sgml
Log Message:
Clarifying documentation to be clear that 'DROP SCHEMA' must be
used to drop the slony schema.
Index: triggers.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/triggers.sgml,v
retrieving revision 1.3
retrieving revision 1.3.2.1
diff -C 2 -d -r1.3 -r1.3.2.1
*** triggers.sgml 13 Oct 2008 21:36:45 -0000 1.3
--- triggers.sgml 17 May 2010 18:20:05 -0000 1.3.2.1
***************
*** 127,133 ****
<listitem><para> If you take a <application>pg_dump</application> of a
! &slony1; node, and drop out the &slony1; namespace, this now cleanly
! removes <emphasis>all</emphasis> &slony1; components, leaving the
! database, <emphasis>including its schema,</emphasis> in a
<quote>pristine</quote>, consistent fashion, ready for whatever use
may be desired. </para> </listitem>
--- 127,133 ----
<listitem><para> If you take a <application>pg_dump</application> of a
! &slony1; node, and drop out the &slony1; namespace(using the DROP SCHEMA command)
! this now cleanly removes <emphasis>all</emphasis> &slony1; components, leaving
! the database, <emphasis>including its schema,</emphasis> in a
<quote>pristine</quote>, consistent fashion, ready for whatever use
may be desired. </para> </listitem>
- Previous message: [Slony1-commit] slony1-engine/src/backend slony1_funcs.v83.sql slony1_funcs.v84.sql
- Next message: [Slony1-commit] slony1-engine/doc/adminguide triggers.sgml
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list