Just because you have a lot of RAM doesn't mean you'll never touch your page file. 64-bit apps are no longer restricted to just using 2GB of RAM per process. If you have some stuff in memory that hasn't been used for a while, Windows will page it out so that you've got more RAM free to use when you start a big app. Otherwise, it will have to page that RAM out when you start it, greatly slowing the process.

That's one reason to leave it alone. Also, if you're running more than 160GB, 8GB is barely a blip. If you're running into the edge of your system drive, you've got too much crap and need to move some off, delete it, or get a bigger system drive.

Quoting test_tube_tony

what is it about adobe that makes it want a pagefile? is it that much of a memory hog?

It's not so much that the app itself is a memory hog, but the act of editing photos and maintaining history on uncompressed image data (A jpg is only compressed when it's sitting on the drive, in memory, it's converted back to uncompressed image data, which is roughly equivalent to (total number of pixels x rgb bit depth) + history of changes). If you have more than a few files open, or do a lot of changes, you can see how memory can get eaten up quickly. Photoshop pages the less-frequently used image data more aggressively even than Windows would in an effort to keep things moving smoothly.