| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Jim Nasby <jim(at)nasby(dot)net> |
| Cc: | bsreejithin <bsreejithin(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: How clustering for scale out works in PostgreSQL |
| Date: | 2013-09-12 18:46:20 |
| Message-ID: | 1379011580.85901.YahooMailNeo@web162901.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Jim Nasby <jim(at)nasby(dot)net> wrote:
> If you setup some form of replication it's very easy to move to
> larger servers as you grow. I'm sure that when Kevin moved their
> database it was a complete non-event.
Yeah, replication was turned on for the new server in addition to
the old one. When everything was ready the web application
configuration was updates so that it started using the new server
for new requests and disconnected from the old server as requests
completed. Zero down time. No user-visible impact, other than
things ran a little faster because of the better hardware.
One generation of old hardware is kept in replication for running
ad hoc queries and to provide availability in case the new one
crashes.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Whittaker | 2013-09-12 20:06:22 | Re: Intermittent hangs with 9.2 |
| Previous Message | Jim Nasby | 2013-09-12 15:18:58 | Re: How clustering for scale out works in PostgreSQL |