Re: minimizing downtime when upgrading
От | Oleg Bartunov |
---|---|
Тема | Re: minimizing downtime when upgrading |
Дата | |
Msg-id | Pine.GSO.4.63.0606161551550.10866@ra.sai.msu.su обсуждение исходный текст |
Ответ на | minimizing downtime when upgrading (snacktime <snacktime@gmail.com>) |
Список | 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@sai.msu.su, http://www.sai.msu.su/~megera/ phone: +007(495)939-16-83, +007(495)939-23-83
В списке pgsql-general по дате отправления: