Mon Jul 12 09:44:50 PDT 2010
- Previous message: [Slony1-bugs] Replication the whole database
- Next message: [Slony1-bugs] [Bug 104] slon core in sched_add_fdset
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rahul Reddy <nilapusa at yahoo.com> writes: > I have implemented slony replication but I have noticed that It > only replicates a table instead of the whole database. Is there any > way I can replicate the whole database instead of a single or > couple of database ? Thanks If you want the entire database replicated, that's actually more of a use case for Continuous Archiving/PITR. <http://www.postgresql.org/docs/8.4/static/continuous-archiving.html> There have been proposals to have Slony-I replicate all tables in a database. Unfortunately, it is almost always the case that people want "all the tables, except for these ones," and making a user interface for "except these ones" is notably troublesome, particularly when my "except these ones" differ from your "except these ones." It's not difficult to use the view information_schema.tables to pull a list of all tables in your database: psql -c "select table_schema, table_name from information_schema.tables where table_type = 'BASE TABLE' and table_schema not in ('pg_catalog', 'information_schema');" Putting this into a list as input for a Slonik script is not terribly difficult, and it seems to me that you probably need to do enough other verification work to ensure that these are the tables you were looking for that further automation wouldn't actually help terribly much. -- output = ("cbbrowne" "@" "ca.afilias.info") Christopher Browne "Bother," said Pooh, "Eeyore, ready two photon torpedoes and lock phasers on the Heffalump, Piglet, meet me in transporter room three"
- Previous message: [Slony1-bugs] Replication the whole database
- Next message: [Slony1-bugs] [Bug 104] slon core in sched_add_fdset
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list