There are two ways to run a replica. You can use either, or both together:


Streaming replication, where the replica makes a PostgreSQL protocol connection to the standby as configured with primary_conninfo in recovery.conf; or
WAL shipping, where the replica runs a restore_command (set in recovery.conf that fetches WAL archives to replay.


See recovery.conf.

Both require that standby_mode be set in recovery.conf.

WAL-E is designed to be used as an archive_command on the master, to store WAL into S3, then as a recovery_command on the replica to fetch WAL. There is no need for a streaming replication connection. You can add one anyway, and it will be used where available, and the system will fall back to WAL archive recovery if it can't connect over streaming replication. Or you can just use WAL-based archiving.

The main advantage of using streaming replication as well is that it's more timely; you don't have to wait until an entire WAL archive is filled and shipped before the replica sees the changes.

For more information see the manual.

How to have remote standby PostgreSQL server in different location (AWS)?
I am currently applying to faculty positions, primarily teaching positions at 4 year colleges and universities. I am told many of these jobs have more than 100-200 applicants. Some of the jobs ads themselves say they get hundreds of applicants, and go on to say something to the effect 'you probably aren't going to hear anything from us', which says to me - 'don't bother us'. I have 3 questions, which overlap:


If I don't hear back from them at all, is it appropriate to contact the department?
If I hear back that they got my application and materials, is it appropriate to contact the department?
People that I know from the business world encourage me to be more aggressive by calling the departments to check in, and even asking if I can come visit the department. I am concerned that this sort of attitude can have a backlash effect. Is this sort of aggressive approach accepted in academia?

