Thanks for the answer.
I see the point with the backup :)
Regards
Thomas
Scot Kreienkamp, 02.02.2009 16:19:
> Probably can. But you're talking about disabling off-host archiving.
> The whole point behind this is prevention in case a host hard drive
> fails... if it fails and you don't use off-host archiving then you've
> lost the files you need to rebuild the database along with the original
> database.
>
> Thanks,
>
> Scot Kreienkamp
> La-Z-Boy Inc.
> skreien@la-z-boy.com
> 734-242-1444 ext 6379
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Thomas Kellerer
> Sent: Sunday, February 01, 2009 7:47 AM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Warm Standby question
>
> Hi,
>
> (Note: I have never used log shipping before, I'm just interested in the
>
> concepts, so I'm might be missing a very important aspect)
>
> I was reading the blog entry about HA and warm standby:
> http://scale-out-blog.blogspot.com/2009/02/simple-ha-with-postgresql-poi
> nt-in-time.html
>
> The image that explained how log shipping works, strikes me as being a
> bit too
> complex.
> <http://1.bp.blogspot.com/_26KnjtB2MFo/SYVDrEr1HXI/AAAAAAAAAEY/ncq_AW-Vv
> -w/s1600-h/pg_warm_standby.png>
>
> According to the picture it basically works like this:
>
> Master -> Copy master archive directory -> Copy to standby archive dir
> -> copy
> to pg_xlogs.
>
> When I look at this chain I'm asking myself, why do I need the two
> archive
> directories?
>
> Why can't the master copy the files directly into the pg_xlogs directory
> of the
> standby server?
>
> Thanks
> Thomas
>
>
>
