Re: Warm Standby - log shipping

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: Warm Standby - log shipping
Дата
Msg-id 494A7819.EE98.0025.0@wicourts.gov
обсуждение исходный текст
Ответ на Warm Standby - log shipping  ("Mark Steben" <msteben@autorevenue.com>)
Ответы Re: Warm Standby - log shipping  ("Mark Steben" <msteben@autorevenue.com>)
Список pgsql-admin
>>> "Mark Steben" <msteben@autorevenue.com> wrote:

> We are at postgresql 8.2.5

You really should update to 8.2.11 or consider going to 8.3.5.

http://www.postgresql.org/support/versioning

> We plan on using the Norfolk server not so much as a recovery
failover but
> as a replicated database
> To run reports and establish a data warehousing environment.  As such
the
> plan is to run  the
> Standby in recovery state for the majority of the day, then
'complete'
> recovery there, bring it
> Online, perform our reporting and data warehousing functions (in
read-only
> mode of course),
> Then bring it back into recovery mode, letting the updates catch up
for the
> next days processing.
>
> My questions are:
>
> 1. Is this a proper usage of log shipping?

Once you complete recovery you don't have a good way back, short of
getting a new base backup.  If you have space, you could stop the
replica server without leaving recovery state, do a copy of the
cluster to another directory, restart your replica, start the copied
cluster's server, complete recovery, and start running your reports.

> 3. I am currently in a state where a log got partially copied and
postgres
> cannot find a valid checkpoint to restart.  What is the best way to
remedy
> this situation?  Pg_resetxlog perhaps?

I'd get a fresh base backup from which to start.

-Kevin

В списке pgsql-admin по дате отправления:

Предыдущее
От: "Mark Steben"
Дата:
Сообщение: Warm Standby - log shipping
Следующее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: Warm Standby - log shipping