Whenever your building a new Drupal site or troubleshooting a problem on an existing site, it helps to have a local development copy to make it easier to do things like populate test data, try new modules, or run xdebug against.
It's pretty easy to move the code around using svn, rsync or my new favorite git. Moving the database is a bit more complicated.
I've gotten in the habit with the MySQL databases of exporting the database into a .sql file, committing it to git, pulling a copy local, then loading into my local MySQL instance.
You can of course do the same thing with the Postgres databases but it's a little different.
First off Backup and Migrate doesn't appear to work properly with PostGres, basically refusing to allow configuration of the source database.
This leaves a couple of options:
drush sql-dump / sql-connect or pg_dump
drush sql-dump is nice because it is db engine agnostic, making the appropriate adjustments based on the db your using.
However even with this method I was experiencing some Notice: unserialize() [function.unserialize]: Error at offset 0 of 22765 bytes in errors on my local machine.