pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Moiz Kothari <moizpostgres@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: 100% failover + replication solution
Date: Tue, 14 Nov 2006 15:11:54 -0500 (EST)
Message-ID: <200611142011.kAEKBse00586@momjian.us> (raw)
In-Reply-To: <82e1a9bd0610300147m7e214893ue1306f1637bb489f@mail.gmail.com>


I wrote this for the 8.2 documentation.  Let me know if it helps or you
have other suggestions:

	http://developer.postgresql.org/pgdocs/postgres/failover.html

---------------------------------------------------------------------------

Moiz Kothari wrote:
> Guys,
> 
> I have been thinking about this and wanted to see if it can be achived. I
> wanted to make a 100% failover solution for my postgres databases. The first
> thing that comes to my mind is doing it using WAL logs. Am attaching the
> diagram for which i will write more here.
> 
> I was thinking if i can have Hotsync the databases using the WAL logs. If
> you see the architecture, the select goes to the SLAVE nodes and the INSERTS
> goes to the MASTER database, that means there should be no transactions
> happening on SLAVES (pure select). not even using "plpgsql". In this
> archecture i wont even mind restarting the SLAVE nodes if i need to.
> 
> I was reading on PIT recovery on postgres, the only current problem i am
> facing with that is, i need to backup the database and move the slaves and
> the apply WAL logs to it. That could be huge amount of transfer and hence a
> longer downtime then moving 16mb WAL log files.
> 
> Can someone help me out here, what i want is a continuous applying of WAL
> logs once i have brought the database up. I want to elimiate the backup of
> master to be restored to the slaves everytime i want to apply WAL to slaves.
> It would be real help if someone can  tell me if it is possible to apply WAL
> logs to the slaves continously as soon as they are created on MASTER. I
> checked other tools available and thougth this would be best approach if it
> works.
> 
> Awaiting reply soon.
> 
> Regards,
> Moiz Kothari

[ Attachment, skipping... ]

> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings

-- 
  Bruce Momjian   bruce@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +



view thread (20+ messages)  latest in thread

Message-ID: <200611142011.kAEKBse00586@momjian.us>
Permalink:  ../200611142011.kAEKBse00586@momjian.us/
Also on:    postgresql.org/message-id/200611142011.kAEKBse00586@momjian.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: bruce@momjian.us, moizpostgres@gmail.com
  Subject: Re: 100% failover + replication solution
  In-Reply-To: <200611142011.kAEKBse00586@momjian.us>
  References: <82e1a9bd0610300147m7e214893ue1306f1637bb489f@mail.gmail.com> <200611142011.kAEKBse00586@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox