Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
PostgreSQL 9.3 beta: Federated databases and more
LWN.net Weekly Edition for May 9, 2013
(Nearly) full tickless operation in 3.10
I don't trust them. I tried PgCluster and it ate my data. So I don't want to try any invasive third-party patches anymore.
It works out-of-box in MySQL, anyway.
PostgreSQL 8.4 released
Posted Jul 1, 2009 23:13 UTC (Wed) by fdr (subscriber, #57064)
Also, 'clustering' (which I take to also mean parallel query execution) is orthogonal to replication. Consider middleware, pl/proxy (also a Skype tool), or just old-fashioned hand-rolled application logic.
Posted Jul 2, 2009 1:29 UTC (Thu) by Cyberax (✭ supporter ✭, #52523)
I.e. two queries should return the same data if they are executed at the same time (of course, not considering other transactions), even if they are executed on different hardware nodes.
Posted Jul 2, 2009 4:00 UTC (Thu) by dlang (✭ supporter ✭, #313)
for postgres, I think the option you would want is plproxy, it makes changes to all boxes in the cluster at the same time and splits queries between machines.
I haven't used it so check that it doesn't have any limitations that will kill you
Posted Jul 2, 2009 5:44 UTC (Thu) by fdr (subscriber, #57064)
Posted Jul 3, 2009 20:27 UTC (Fri) by hingo (guest, #14792)
Posted Jul 1, 2009 23:20 UTC (Wed) by dlang (✭ supporter ✭, #313)
there are many horror stories around about MySQL replication eating people's data. being 'built-in' doesn't eliminate that possibility.
there are many different ways to do replication and failover for databases, each has advantages and disadvantages. Postgres (through these external projects) has most of the range covered, the hit-standby,synchronous-write mode is missing, and that is what is going to be added in 8.5
it may be that once this gets in, some of the other solutions that need patches will ask to be added as well, but so far it's been a case of trying to to imply that one solution is better than all the others by including it and not the others
most of the different replication solutions that are available for postgres are significantly better than all of the others, for a specific set of requirements.
Posted Jul 1, 2009 23:53 UTC (Wed) by akumria (subscriber, #7773)
google: "mysql replication horror story"
Presumably they would be so widely known that showing up in the first 10 hits on google is a reasonable test.
Hmm - which of those non-stories was the 'many' that you had in mind?
Posted Jul 2, 2009 0:33 UTC (Thu) by dlang (✭ supporter ✭, #313)
Posted Jul 2, 2009 0:59 UTC (Thu) by akumria (subscriber, #7773)
Please do not weasel out of pointing out information that could be beneficial to those of us attempting to make a balanced consideration between the two.
If you have any stories you can point to -- let us know; I would appreciate the information. It would help to inform my opinion about MySQL and the merits (or otherwise) of it's replication.
Otherwise your comment just serves to inform my opinion about hyperbole on the Internet and its continuing rise.
Posted Jul 2, 2009 4:09 UTC (Thu) by dlang (✭ supporter ✭, #313)
this was without any system crashes
no, I don't know of Internet links that document this.
my prior post was intended to make the point that doing a google search for "mysql replication horror story" and not finding a real one in the first ten hits has very little, if anything to do with the quality or lack of quality of mysql (or postgres) replication.
I never like to hear of anyone loosing their data, but to then make the claim that if the replication tool was built-in instead of a seperate project it would not have happened, and that mysql 'just works' as an example of this always being true is just not a valid chain of logic.
Posted Jul 2, 2009 18:00 UTC (Thu) by yoe (subscriber, #25743)
"Results 1-10 of about 122,000 for mysql replication broken (0.60 seconds)"
Then again, what with mysql being a horrible toy, clustering being broken is hardly a suprise.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds