From: | "Carlos Oliva" <carlos(at)pbsinet(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Upgrading Database: need to dump and restore? |
Date: | 2009-06-04 13:11:41 |
Message-ID: | h08h69$lqs$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)gmail(dot)com> wrote in message
news:2f4958ff0906040549u53bafe7br772033214d43e262(at)mail(dot)gmail(dot)com(dot)(dot)(dot)
On Thu, Jun 4, 2009 at 1:23 PM, Carlos Oliva <carlos(at)pbsinet(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-06-04 13:48:17 | Re: Division by zero |
Previous Message | Grzegorz Jaśkiewicz | 2009-06-04 12:49:20 | Re: Upgrading Database: need to dump and restore? |