Messing around with version control is often not ones highest priority. Whether learning Mercurial or Git is a good investment of your time will have much to do with your particular circumstances.
However, there are real advantages of distributed version control. Most compelling to me is that it separates the act of committing code (and thus having it always available for all time) and the act of inflicting that code on the rest of the team. If I'm using Git, I'll do a local commit at least every hour, and push to the central repository several times a day. If I'm using SVN, I only commit when my code is appropriate for public consumption, and thus may work for five or six hours without any commits.
So read a little more about it, and see if the benefits are compelling to you. If it seems to be solving problems that you don't yet have, then it isn't yet time for you to mess with it. But if you find yourself intrigued, go for it.
For Git, the best resource is http://progit.org/book/
For Mercurial, a great read to think right is Joel's tutorial: http://hginit.com/