solution (i.e. slony) or just a simple pg_dump/pg_restore script would
work. Ideally I'd like to have as little additional load on the production
server as possible. Also, the production db is currently at 12GB (and
growing steadily), so I'm a bit concerned that doing a full pg_restore
every day might become infeasible at some point.

Any thoughts?

Thanks,
Ryan

--bcaec54fb81a2f30b704cba91c99
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,<div><br></div><div>I&#39;d like to replicate my production database to =
2 separate Postgres instances --- one for reporting and one for staging. Th=
e main requirement is that the data needs be current up to the state of the=
 production db the day before.=C2=A0</div>

<div><br></div><div>From what I&#39;ve read it seems like using an asynchro=
nous replication solution (i.e. slony) or just a simple pg_dump/pg_restore =
script would work. Ideally I&#39;d like to have as little additional load o=
n the production server as possible. Also, the production db is currently a=
t 12GB (and growing steadily), so I&#39;m a bit concerned that doing a full=
 pg_restore every day might become infeasible at some point.</div>

<div><br></div><div>Any thoughts?</div><div><br></div><div>Thanks,</div><di=
v>Ryan</div>

--bcaec54fb81a2f30b704cba91c99--