Hey Marcus
You said a very interesting thing regarding the mysql on a 32 bit enviromnent.
Currently I have as a a pk, an autoincrement value as int(9)
I should be able to reach 999.999.999 records, right?
Placing the autoincrement as 10, I will have 10x less so I will have 99.999.999 (99
million records).
Is this correct?
Since I already have around 125.000.000 records, I guessing implementing this without
clearing some records, will pretty much ruin everything.
Any advice?
I can use an autoincrement of 5 for instance. Guessing having master 1 with offset of 1
and master 2 with an offset of 2, I feel i will not have much of a problem here.
Ricardo
On 27 Oct 2011, at 11:59, Marcus Bointon <marcus@stripped> wrote:
> On 27 Oct 2011, at 12:52, Ricardo Freitas wrote:
>
>> If I'm to replicate this info into a database with different offsets, this
>> relationship would failed cause the index_id wouldn't change however the
>> table_index ph would change.
>
> It doesn't work like that. The offset only applies to newly created records on that
> specific server, not to records received via replication. This means it's not a problem.
>
> Marcus
> --
> Marcus Bointon
> Synchromedia Limited: Creators of http://www.smartmessages.net/
> UK info@hand CRM solutions
> marcus@stripped | http://www.synchromedia.co.uk/
>
>
>
>
> --
> MySQL Replication Mailing List
> For list archives: http://lists.mysql.com/replication
> To unsubscribe: http://lists.mysql.com/replication?unsub=1
>
