Mon Dec 17 05:40:58 PST 2007
- Previous message: [Slony1-general] Different indexes on slave
- Next message: [Slony1-general] error while replicating between postgres 7.4 and 8.1 version
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
James Tucker a écrit : > > Hi All, > > We're currently running slony to replicate to our DR site. We're > looking at creating another reporting database at each site so our > application can use that for reports etc, and the master for our > normal oltp load. The reporting database only needs a subset of the > tables included in the DR set. > > I have 2 questions. > > Is there any reason we can't create different indexes (aimed at faster > reports as apposed to OTLP) on the reporting slave ? None. It's one of Slony advantages. Indexes can differ. > > Currently I just have one set that includes all our tables, am I able > to create another set with just a selection of those tables ? Or > would I need to recreate my existing set, splitting it. > > i.e. > > set1 = table1, table2, table3 > > set2 = table1, table2. A table can't appear in two different sets. For instance, which replication set will you break when executing a script that alters that table? Regards, -- Stéphane SCHILDKNECHT Président de PostgreSQLFr Tél. 09 53 69 97 12 http://www.postgresqlfr.org
- Previous message: [Slony1-general] Different indexes on slave
- Next message: [Slony1-general] error while replicating between postgres 7.4 and 8.1 version
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list