| From: | Volkan YAZICI <yazicivo(at)ttmail(dot)com> |
|---|---|
| To: | Jason Long <mailing(dot)list(at)supernovasoftware(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Slony vs Longiste |
| Date: | 2008-09-24 05:43:48 |
| Message-ID: | 87abdyxfmz.fsf@alamut.mobiliz.com.tr |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jason Long <mailing(dot)list(at)supernovasoftware(dot)com> writes:
> I need to set up master vs slave replication.
>
> My use case is quite simple. I need to back up a small but fairly
> complex(30 MB data, 175 tables) DB remotely over T1 and be able to
> switch to that if the main server fails. The switch can even be a
> script run manually.
>
> Can someone either comment in as much detail as possible or point me
> to a comparison of Slony vs Longiste. Or some other option I have not
> heard of?
You can also consider using pg-pool[1] or sequioa[2] which will
automatically handle high-availability if any of the servers fails.
Regards.
[1] http://pgpool.projects.postgresql.org/
[2] http://sequoia.continuent.org/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomasz Ostrowski | 2008-09-24 07:40:37 | Re: pg_dump | pg_sql: insert commands and foreign key constraints |
| Previous Message | Bruce Momjian | 2008-09-24 03:20:01 | Re: PostgreSQL future ideas |