From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
---|---|
To: | snacktime <snacktime(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: minimizing downtime when upgrading |
Date: | 2006-06-16 11:52:27 |
Message-ID: | Pine.GSO.4.63.0606161551550.10866@ra.sai.msu.su |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 15 Jun 2006, snacktime wrote:
> Anyone have any tips for minimizing downtime when upgrading? So far
> we have done upgrades during scheduled downtimes. Now we are getting
> to the point where the time required for a standard dump/restore is
> just too long. What have others done when downtime is critical? The
> only solution we have been able to come up with is to migrate the data
> on a per user basis to a new database server. Each user is a
> merchant, and the data in the database is order data. Migrating one
> merchant at a time will keep the downtime per merchant limited to just
> the time it takes to migrate the data for that merchant, which is
> acceptable.
>
> Any other ideas?
we use replication package slony for upgrading.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru)
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83
From | Date | Subject | |
---|---|---|---|
Next Message | Nitin Verma | 2006-06-16 12:04:50 | Re: VACUUMing sometimes increasing database size / sometimes |
Previous Message | Florian G. Pflug | 2006-06-16 11:18:19 | Re: VACUUMing sometimes increasing database size / sometimes |