Short answer - there's no such solution yet for PostgreSQL if you need online readonly slaves.

There're two major development projects currently going on in this area which are included in PostgreSQL 9.0 (Spring/Summer 2010), namely:

• Synchronous Replication:

http://wiki.postgresql.org/wiki/NTT's_Development_Projects

• Read only hot standby slaves:

http://wiki.postgresql.org/wiki/Hot_Standby

which in combination aim to achieve the ease of use of MySQL-style replication minus the bugs/issues MySQL has plus the reliability users know from PostgreSQL.

All of this was kicked off by a manifest from the PostgreSQL Core Team in 2008:

http://archives.postgresql.org/pgsql-hackers/2008-05/msg00913.php

The PostgreSQL replication solutions to this day with the largest user base are Slony-I (more expensive for writes, makes schema changes fiddly), WAL shipping/walmgr (Slaves can't be used online) and pgQ/londiste from Skype/Skytools (more tools/building blocks than a finished solution).

I've written a few things on Log Shipping, walmgr and Slony-I, see

http://blogs.amd.co.at/mt/mt-search.cgi?blog_id=1&tag=pgrep&limit=20 for more information.

Please be aware that in PostgreSQL, your cluster data directory is a self-contained unit that cannot reliably be restored in parts, as per the documentation here.

Your best hope is to use the full data directory of the old server and to start a server on it, then restore from a dump of the database you get from there:

1. Get a postgresql.conf that fit the configuration on the new host going (orient yourself by the files in the old - which you change here - and new data directories)
2. Find out the user name of the old installation's PostgreSQL superuser - most likely postgres.
3. Create this user name (UNIX user) on the new host, unless it's already there.
4. Give (chown) the old data directory to that user, unless the uid matches the one on the old server.
5. Configure pg_hba.conf in the old data directory to allow connections from local users to the same postgres user name (this is normally the default, but check).
6. Run the old database cluster as the UNIX user with the same name as the old data directory's superuser, e.g. for user postgres:

   sudo -u postgres postgres -D old_data_directory
   
   or with su:
   
   su postgres
   postgres -D old_data_directory
   

7. dump the old database, again with the usual user name, postgres:

   sudo -u postgres pg_dump -p /path/to/socket/for/old/directory database_name > dump_file.sql
   
   becoming postgres with su analogous to above

8. adapt the dump_file.sql to the new server's user names etc; create the empty database with appropriate ownership there
9. scan the database into the new server:

   sudo -u postgres psql -p /path/to/socket/for/new/directory new_database_name
   
   once again, getting postgres privileges using su analogous to above
   
   

That should get you set, or at least show a good path to get there.