Wed May 12 06:42:28 PDT 2010
- Previous message: [Slony1-general] unable to create replication set for a table not having private key
- Next message: [Slony1-general] unable to create replication set for a table not having private key
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5/12/2010 1:30 AM, Jayadevan M wrote: > > I am not able create replication set for a table not having private > key. Is there anything that can be done? > This is what you are looking for? > http://www.slony.info/adminguide/slony1-1.2.6/doc/adminguide/stmttableaddkey.html > > Regards, > Jayadevan This is certainly not what he is looking for. This command is no longer supported as of Slony-I version 2.0. In version 2, the various "catalogue breakages" done in PostgreSQL versions prior to 8.3 are being eliminated so that schema dumps may be taken from any node. That leaves the "kludgy" columns created via TABLE ADD KEY as the only thing that prevents SLONIK UNINSTALL NODE from being comprised of the SQL statement drop schema _ClusterName cascade;. Jan -- Anyone who trades liberty for security deserves neither liberty nor security. -- Benjamin Franklin
- Previous message: [Slony1-general] unable to create replication set for a table not having private key
- Next message: [Slony1-general] unable to create replication set for a table not having private key
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list