psql -c "CREATE USER replicator REPLICATION LOGIN ENCRYPTED PASSWORD 'thepassword';"

listen_address = # make sure we're listening as appropriate
wal_level = hot_standby
max_wal_senders = 3
checkpoint_segments = 8
wal_keep_segments = 8 

host  replication     replicator      10.10.10.1/32              md5

 rm -rf /usr/local/pgsql/data

pg_basebackup -h 10.10.10.2 -D /usr/local/pgsql/data -U replicator -v -P

  standby_mode = 'on'primary_conninfo = 'host=10.10.10.2 port=5432 user=replicator password=thepassword sslmode=require'trigger_file = '/tmp/postgresql.trigger'

[postgres@pg200 pgsql]$ ./bin/pg_ctl -D ./data start
pg_ctl: another server might be running; trying to start server anyway
server starting
[postgres@pg200 pgsql]$ LOG:  database system was interrupted while in recovery at log time 2013-09-27 17:28:27 CST
HINT:  If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
LOG:  entering standby mode
LOG:  consistent recovery state reached at 0/5012F78
LOG:  redo starts at 0/5012EE0
LOG:  record with zero length at 0/5012F78
LOG:  database system is ready to accept read only connections
LOG:  streaming replication successfully connected to primary

[postgres@pg200 ~]$ cd /usr/local/pgsql/
[postgres@pg200 pgsql]$ ./bin/psql
psql (9.2.4)
Type "help" for help.postgres=# \lList of databasesName    |  Owner   | Encoding |   Collate   |    Ctype    |   Access privileges
-----------+----------+----------+-------------+-------------+-----------------------postgres  | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | template0 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +|          |          |             |             | postgres=CTc/postgrestemplate1 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +|          |          |             |             | postgres=CTc/postgres
(3 rows)postgres=# \dList of relationsSchema | Name | Type  |  Owner
--------+------+-------+----------public | test | table | postgres
(1 row)postgres=# select * from test;id
----123
(3 rows)postgres=# insert into test values(4);
INSERT 0 1
postgres=# 

[postgres@pg200 ~]$ cd /usr/local/pgsql/bin
[postgres@pg200 bin]$ ./psql
psql (9.2.4)
Type "help" for help.postgres=# select * from test;id
----1234
(4 rows)postgres=# 

http://www.postgresql.org/docs/current/static/app-pgbasebackup.html

pg_basebackup is used to take base backups of a running PostgreSQL database cluster. These are taken without affecting other clients to the database, and can be used both for point-in-time recovery (see Section 24.3) and as the starting point for a log shipping or streaming replication standby servers (see Section 25.2).pg_basebackup makes a binary copy of the database cluster files, while making sure the system is automatically put in and out of backup mode automatically. Backups are always taken of the entire database cluster, it is not possible to back up individual databases or database objects. For individual database backups, a tool such as pg_dump must be used.The backup is made over a regular PostgreSQL connection, and uses the replication protocol. The connection must be made with a superuser or a user having REPLICATION permissions (see Section 20.2), and pg_hba.conf must explicitly permit the replication connection. The server must also be configured with max_wal_senders set high enough to leave at least one session available for the backup.

create table test01(id integer, val char(1024));
insert into test01 values(generate_series(1,1228800),repeat( chr(int4(random()*26)+65),1024));

[postgres@pg200 ~]$ cd /usr/local/pgsql
[postgres@pg200 pgsql]$ ./bin/pg_ctl -D ./data start
server starting
[postgres@pg200 pgsql]$ LOG:  database system was shut down in recovery at 2013-09-30 14:51:27 CST
LOG:  entering standby mode
LOG:  consistent recovery state reached at 0/5013A48
LOG:  redo starts at 0/50139B0
LOG:  record with zero length at 0/5013A48
LOG:  database system is ready to accept read only connections
LOG:  streaming replication successfully connected to primary
FATAL:  could not receive data from WAL stream: FATAL:  requested WAL segment 000000010000000000000011 has already been removedLOG:  invalid magic number 0000 in log file 0, segment 17, offset 14467072
LOG:  streaming replication successfully connected to primary
FATAL:  could not receive data from WAL stream: FATAL:  requested WAL segment 000000010000000000000011 has already been removed