Tag Info

Hot answers tagged

2

The database name has to be replication as all does not cover replication connections. host replication postgres 127.0.0.1/0 trust The PostgreSQL documentation further says: The value replication specifies that the record matches if a replication connection is requested (note that replication connections do not ...


2

We don't need automatic failover, and we don't necessarily need the data to be replicated in real-time: once every 5-15 minutes would be fine. First thing you need to do is to change your database recovery model to FULL as logshipping is not supported in simple mode. In your scenario, logshipping would be best choice IMHO without the need to upgrade to ...


2

You're right about each of your options. Log Shipping is perhaps the easiest way to almost accomplish what you want, but there is the drawback that you won't be able to read from your secondaries while the logs are being restored. If your goal is simply to become more highly available in case something bad happens, I advise you to at least get your backup ...


2

well, you cannot switch back easily. what you can do is to use the old backup method: SELECT pg_start_backup('whatever'); rsync the data dir SELECT pg_stop_backup(); this is the best way as not all the data has to be transported over the network. i definitely recommend this replacement for pg_basebackup because it is the only RELIABLE way to get things ...


2

You should put everything on a level playing field. How ? Without proper tuning, it is possible for older versions of MySQL to outrun and outgun new versions. Sep 25, 2013 : Why should I use InnoDB and MySql instead of XtraDB and MariaDB? Mar 26, 2012 : Percona vs MySQL Nov 24, 2011 : Why mysql 5.5 slower than 5.1 (linux,using mysqlslap) Oct 05, 2011 : ...


1

MongoDB at least to current version 2.6+ for sure does not support that as build-in functionality. I guess because a replica set using selective replication won't be consistent. There is a feature called filtered replication in Couch but never tried it: http://wiki.apache.org/couchdb/Replication#Filtered_Replication


1

I don't have experience of your exact situation, but could you use: auto_increment_increment=3 auto_increment_offset=1 [then 2 and then 3] on your different masters, so that each one generates a different set of id's. e.g. server 1: 1, 4, 7 server 2: 2, 5, 8 server 3: 3, 6, 9


1

I know this is an old question but I think I just found an answer. If you modify the sample config (initdb -D /tmp/foo -s | grep POSTGRESQL_CONF_SAMPLE) and set wal_level=hot_standby in the sample config, then the base and WAL files will be created appropriately and Postgres will start and try to connect to the master DB. I haven't figured out how to pass ...


1

This is a permissions issue and you can find more details in the verbose agent log. Verify that your replication agent process accounts have the necessary permissions listed in the section Permissions That Are Required by Agents in Replication Agent Security Model. Note that Microsoft recommends that you use a Windows accounts for replication agent process ...


1

Some might say depends how big the databases are; I think regardless of the size, accessing the databases directly instead of having a "local" mySQL database to query would be best, for the following reasons: No need for disk/memory/maintenance of the mySQL database If the updates to the various databases happen every few seconds, and the users may only ...


1

I believe you are running into the issue described in Subqueries that you define on merge articles are not re-evaluated. From the article the cause is: This behavior occurs because the query is not re-evaluated and the row is not propagated as part of replication when you update a row in a table that is referenced by a subquery. Although you can ...


1

In a previous role at a different Organisation to where I am now employed, we faced a similar decision whereby the GUID issue (as pointed out in the link) was a factor for us (both Width and poor choice regarding Index fragmentation) - but we needed to move to Transactional Replication (Peer-to-Peer) to allow our Sites to be Geographically separated. In our ...


1

I think you what you are describing is a replication topology called a Star Topology I wrote about that before Apr 18, 2013 : Single slave - multiple master MySQL replication (Approach #1) Apr 28, 2011 : MySQL in star topology (ServerFault) Apr 26, 2011 : MySQL in star topology (Stack Overflow) In that event, the Central Server must serve as a Slave in ...


1

You can try following method Flush tables with read lock on master(It will lock the master) show master status use this position accordingly in change master to command unlock tables(It will unlock master) Hope it helps.



Only top voted, non community-wiki answers of a minimum length are eligible