-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Edward Zeng wrote:
| Hello every one,
|
| I am a fresh user in Slony and Postgresql,
|
| Right now we need to separate the slave and master database.
| But each time I tried to update or delete the slave database, it always
| report that the slony will handle the update for me. I can not update
| the table even using "postgres" user. I have already stop the slony. but
| it seem the table still handle by slony how come?

You need to use the Slonik command UNINSTALL NODE in a Slonik script to
restore that subscriber node to an unlocked state.

See the Slonik command summary:

UNINSTALL NODE Synopsis: UNINSTALL NODE ( <options> );

Description: Restores all tables to the unlocked state, with all
original user triggers, constraints and rules, eventually added Slony-I
specific serial key columns dropped and the Slony-I schema dropped. The
node becomes a standalone database. The data is left untouched.
ID = <ival> Node ID of the system to uninstall.

Example:

~   UNINSTALL NODE (     ID = 3 );
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBa+ipCVn6LJfHIAIRAvHYAJ4x51tjz6HqcR3SCDa9ZONYxFhMqACg8ddB
t1L6QL5MhsI21nYU3JnG4C4=
=F2Pn
-----END PGP SIGNATURE-----