Tag Info

Hot answers tagged

3

Since your problem is a conflict between constant updates and being able to run reports without facing deadlocks, I would recommend you consider using READ_COMMITTED_SNAPSHOT isolation set ON. This also has overhead, but usually prevents most deadlocking situations. (Nothing is magic, of course.) You should read the details at: ...


2

The index data order on disk for text columns depends on the locales provided by the underlying operating system. The same locales (that is, with the same name) may differ between operating systems on the order rules, even on simple things. As an example this question: PostgreSQL 9.1 streaming replication problem: replica fails to use an index properly ...


2

Every replication event generated by the master includes the error code that resulted from execution of the query that generated the event. This is usually "success" (0, no error). When the slave executes a query, it expects the error it encounters to be the same error as the master encountered (again, usually "no error"). When this doesn't happen, ...


1

1) Any INSERT, UPDATE, ALTER etc type Query executed on the Master will be written to the Binary log, causing the MASTER_LOG_POS to increase Furthermore, if the Master is receiving updates from another Master (in a Master to Master setup), AND if you have LOG_SLAVE_UPDATES enabled these will be written to the Binary Log as well. Each time you restart the ...


1

Maybe you are experienceing what is described at the end of the following article: http://www.niwi.be/2013/02/16/replication-status-in-postgresql/ In a very busy database, with many writes per second, this number will remain fairly accurate. However, in a system where there are few writes, the "replication_delay" will continually grow because the last ...


1

As no one got back to me (fair enough - maybe you've got jobs too!) I have tested this. We didn't use this method in the end for the production task because the powers that be decided it was ok/best to use 7-Zip to split the single .bak file. However, the answer is - you only need to specify the a file of the set and it works fine (I did this on my test ...


1

After doing some online search,I found what you needed,hope my answer helps you. Answer 1 Note: It Only works with transactional and transactional peer to peer replication T-SQL script which you can use to monitor the status of transactional replication and performance of publications and subscriptions. Things to be considered before executing the ...


1

Looks like the pertinent part (in this case) was to ensure that both the parent and child tables are contained within a single publication; once we did this, then everything started to behave as it should, and 30 or 40 tests later we haven't seen any failures. At a guess... this means that both tables' log entries will be read by the same log reader job on ...


1

For purposes of this discussion, there is only one way to replicate from one MySQL server to another, and the post that you linked to does seem to describe it correctly. In this setup, the slave server needs to have the ability to establish a tcp connection to the master on port 3306. (The master never initiates this connection, so the connection only needs ...


1

The politically correct answer would be that you cannot perform MySQL Replication from a newer Master to an older Slave. You proven the politically correct answer to be wrong. Notwithstanding, the correct answer is you shouldn't do it, at least not for very long. Consequently, I have a very strong warning for you: It can be very unstable and you should ...



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