| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | salah jubeh <s_jubeh(at)yahoo(dot)com>, pgsql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: SR: pg_xlog |
| Date: | 2013-08-27 08:29:24 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17C08DB1@ntex2010a.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
salah jubeh wrote:
> I have a question regarding streaming replication:
>
> When pg_xlog needs to be shipped in streaming replication and when not? I have faced a different
> issues in two existing setups, in the first setup, when shipping the pg_xlogs a time line issue has
> arisen, and in another setup, when not shipping the log files i get -the database system is starting
> up- Fatal error.
You don't need log shipping for streaming replication as such.
The time line problem should be solved in PostgreSQL 9.3.
But it is still a good idea to use log shipping:
As you describe, you will usually need archived WALs to start replication,
unless the base backup is really recent.
Another case is when there is an interruption or the standby cannot
replicate fast enough. Then replication will fall behind and might
need WAL archives to catch up.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yelai, Ramkumar IN BLR STS | 2013-08-27 08:34:05 | Pgbouncer help |
| Previous Message | salah jubeh | 2013-08-27 08:09:02 | SR: pg_xlog |