Percona is widely recognized as a world-class open source database software, support, and services company. The organization is dedicated to helping businesses make databases and applications run better through a unique combination of expertise and open source software. Percona works with numerous global brands across many industries creating a unified experience to monitor, manage, secure, and optimize database environments on any infrastructure.
Percona equips organizations with the freedom to choose, the freedom to create, and the freedom to make a difference - helping them scale and innovate with speed as they grow. For more information, visit www.percona.com.
Great imitative. I have been playing with it for past few days and must say, its very useful. And one question, how can I use mongodb 7.x.x. Currently, its not showing version above 6.0.97. Thanks
Having made thousands of contributions to open source over several years I'm at the point of just being pissed of by people who want to use others to work for free just to mirror their product commercially. SSPL has not a single disadvantage for people who just want to use mongo as a database in their application, even when it's a commercial application. It just affects providers who offer mongo as a service. So eventually I started to like Projects with such licensing due to respect for other developers work and for me personally, this license change speaks rather for the project than against it.
Hi Brad, it was a fantastic a presentation on performance and usage of Indexes. Please address my queries related to Indexes. 1. If a Composite Index is created on the frequently accessed columns, can we drop individual indexes on the columns created from a table on the same columns to avoid Index merge?
Hi, I am using gearman with naemon monitoring server to distribute jobs across the workers which are located in different world regions. What could be a reason for workers to be loaded unevenly? I mean some of them tends to do more jobs than others even resources are enough for more jobs to be done in parallel. Is network latency could be a reason? Is there any tricks to balance them? Thanks!
I really liked the video. When you are explaining the Transaction ID Wraparound concept is a bit confusing. You would have explained with some numbers.
Just finished the video. Absolutely first rate as far as it went. I think perhaps Jim should have ended with an idealized game plan, summarizing all of this hard won knowledge as an abstract tactical roadmap. I will never have any contact will Oracle at any level, but it helps enormously for me to understand what makes Postgres distinct within the database space.
When porting a system, it's often good to get the replacement running early, in any way, shape or form. Patching over the "dual" problem is a way to there sooner. I think the point here is that patching "dual" gets you to a place where you can do more scouting. At the same time, the real portability path should prioritize drilling into the superficial Oraclysms up front, to make this kind of thing unnecessary.
favorite command is \x. It toggles a expanded records behavior. Type it once and it behaves as if every query ended in \G for mysql users. Type \x again to turn it off.
