Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

10
  • 1
    You are correct about 48 bits but it is a CPU limit deliberately. See en.wikipedia.org/wiki/64-bit#Limitations and en.wikipedia.org/wiki/X86-64#Virtual_address_space_details Commented Sep 26, 2011 at 16:55
  • Although your answer is not MySQL-specific, I can relate to your bird's eye view of the OS, so +1 for that. Just to keep things in perspective, please remember the "guys at MySQL" are Oracle. Commented Sep 26, 2011 at 16:55
  • @gbn I was only pointing out that that's the limit everyone refers to for Linux, and I don't think that's accurate, but I can't speak to the Linux internals. But you're correct, everyone refers to the hardware limits. Commented Sep 26, 2011 at 17:04
  • 1
    @RolandoMySQLDBA true, but without an OS to guide us, the answer has to be about the OS. And while it's true today that "the guys at MySQL are at Oracle", that doesn't mean that those guys have the experience per-se of the long-standing Oracle systems-dev gurus, nor does it mean that the team for MySQL has any desire to provide this construct (whereas the Oracle team may have the desire to provide the construct as asked above) .. tl;dr: meh, two different teams. Commented Sep 26, 2011 at 17:06
  • @jcolebrand : I believe Oracle has the expertise (they exercise it within Oracle10g/11g). However, it's the desire part towards MySQL that strikes the biggest chord. +1 on your last comment. Commented Sep 26, 2011 at 17:22