Re: Upgrading Database: need to dump and restore?

Поиск
Список
Период
Сортировка
От Carlos Oliva
Тема Re: Upgrading Database: need to dump and restore?
Дата
Msg-id h08h69$lqs$1@news.hub.org
обсуждение исходный текст
Ответ на Upgrading Database: need to dump and restore?  ("Carlos Oliva" <carlos@pbsinet.com>)
Ответы Re: Upgrading Database: need to dump and restore?  (Bill Moran <wmoran@potentialtech.com>)
Список pgsql-general
I think that I understand.  Would we need to stop the databse and then do
the copy?  Is this the state to which you are refering?  If the tables never
changed after a week or so, what else would change in the database for these
tables after a month, two months, or a year?  Would we need to put the
databse in the correct state a week later, a month later, a year later?
""Grzegorz Jaskiewicz"" <gryzman@gmail.com> wrote in message
news:2f4958ff0906040549u53bafe7br772033214d43e262@mail.gmail.com...
On Thu, Jun 4, 2009 at 1:23 PM, Carlos Oliva <carlos@pbsinet.com> wrote:
> In which state do we need to put the db? We can use both types of backup
> strategy. We can pg_dump the table and copy the tablespace folder along
> with anyhting else that we may need.
Well, not quite. Pg_dump is fine, but you can't just copy data itself,
when server is running.


--
GJ

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



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

Предыдущее
От: Grzegorz Jaśkiewicz
Дата:
Сообщение: Re: Upgrading Database: need to dump and restore?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Division by zero