Upgrading Berkeley DB databases

Question

Okay, so I did a pacman -Syu this morning, and when it upgraded the package "db" I got the message that it is a major version upgrade and that I should consider running db_upgrade on Berkeley DB databases.
Well, since i am very well disciplined in the monkey-see. monkey-do school of computer operation (and really have no idea what I'm doing), I diligently began searching the forums, the wiki and even googlled the Internet to better inform myself before attempting such an upgrade.
And yes, just like anything else that one attempts to research out there in cyberspace, there's a seemingly infinite amount of information available. There's just one little problem: it's all way over my head and completely meaningless to me.
So, does anybody have any quick and easy advice?
(There's nothing exotic about my computer... it's just an old Compaq Deskpro PIII-800 with a Fluxbox desktop that I use for everyday websurfing, email, youtubes and other nonessential personal activities)

Answer 1

Willie:
Wow.  That's grist for the mill, eh?
Your post explains that you looked at the Wiki, Googled, did a search on the Forums, and then did not understand what you found.  You were then told to look on the internet, check the Wiki, go to the website of the outfit that created the package, and look for information.
I did not bother to give the source for the info I found and tried to explain to you.  Whether I got any of it right was not mentioned.
Shame, shame on both you and me!  Aren't we a couple of jerks?
Your candid admission that you are having trouble making sense of what you found is an expression of a real problem.  How is the newcomer to get to the level where he can make use of the resources suggested to him?
I posted some comments about the Arch Wiki entries on Makepkg, Creating Packages, and PKGBUILD.  I suggested a number of things, including the claim that if a Wiki entry is complete, as opposed to written for people who do not need it, no one is harmed.  I suggested that advanced users would simply read the text quickly.
Responses were basically of three types: first, Arch is for experienced users.  Second, "you will not be spoon fed."  Third, I was told to re-write Wiki entries to suit myself.
I have considered the third response seriously, but I have a life.  My point was not, "I can do it better than you guys can," but, "You can do it so you help everybody."
I insist that it IS possible to write on two or three levels, such that the Expert gets what he needs, the Intermediate User learns more, and the Newcomer is able to study the text to advantage.  The use of glossaries, indented paragraphs, () and [], or even colors, can make it easy for the reader to find and learn at his level.  Yes, the author has to put a little thought into how to set things up, but it is not hard.
The resulting text should be demystifying, transparent, cogent, and genuinely helpful to everyone.
As long as an elite is in the driver's seat, the new arrival's prospects will be less than optimum.  I'm not suggesting that he should be exempted from reading and practicing and learning; I'm suggesting that not all advice is of equal quality.  Look at what you got.
I'd like to make a genuine contribution to Arch, because I consider it a wonderful distro.  Maybe I could chip away at its social and informational problems, but there are only so many hours in a day.  Not only that, there is too much I simply don't know.
OK, now to try to post this without getting logged out automatically a third time.  Writing everything twice is getting tiresome.