Re: Backup and Recovery (revisited)

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Backup and Recovery (revisited)
Дата
Msg-id 200202222239.g1MMdR128904@candle.pha.pa.us
обсуждение исходный текст
Ответ на Backup and Recovery (revisited)  (Naomi Walker <nwalker@eldocomp.com>)
Список pgsql-admin
Naomi Walker wrote:
> In the past, several of you have mentioned that adding backup and recovery
> features to Postgres (specifically, point in time recovery), was important
> to you and/or your company.  For one reason or another, it keeps getting
> shoved off the list of features for the next release.
>
> I'd like to organize a group of postgres users to hurry along this process
> by throwing some money at the problem.  My company is willing to pony up
> some of the cost.  I'd like very much to share the cost of making this
> happen with others.  I've gotten a quote from Red Hat for the work, and it
> was insane/excessive, so that is out of the question.
>
> To the group, then, would any of you out there be willing to participate in
> such a venture, either on the financial support or coding side?
>
> I believe Postgres is an excellent database, but without this feature, some
> companies will look elsewhere for a database management systems.  The more
> people that use Postgres, the better for all of us, and this is a critical
> piece..

One use of replication can be point-in-time recovery.  The log of
replication messages can be played back against a nightly backup to
restore the system to the current state.  It would be nice to hit both
of these at the same time.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

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

Предыдущее
От: s.chava@wcom.com (Srinivasa Rao Chava)
Дата:
Сообщение: plpgsql error
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: shared_buffers and effective_cache_size