On Thu, Aug 12, 2010 at 3:19 PM, David E Jones <[email protected]> wrote: > > As Jacques mentioned chances are you'll still have a better experience with > Postgres when it comes to concurrency issues, in the way they manage > transactions and locking in addition to the timestamp resolution issue. >
The idea of migrating a production system from MySQL to Postgres stops my heart. We depend on MySQL's live replication feature for one thing, and the only issue we've had so far that makes us even consider the database, is because the delegator is giving us a data integrity problem. I'm happy to have the confirmation that the problem is not just because we're doing it wrong. We are working a solution into the delegator so that the application can request locks, since it's a pretty unusual case where it is actually a problem. Unfortunately, the problem manifests with inventory counts, which for us is a pretty big issue. Reading ahead, I'm really interested in the nested transaction problem. Since you're strongly suggesting Postgres, do you have any advice for migrating a live system between databases, hopefully from an Entity perspective? -- James McGill Phoenix AZ
