Search Postgresql Archives

Re: Upgrading Database: need to dump and restore?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx> wrote in message 
news:2f4958ff0906040549u53bafe7br772033214d43e262@xxxxxxxxxxxxxxxxx
On Thu, Jun 4, 2009 at 1:23 PM, Carlos Oliva <carlos@xxxxxxxxxxx> 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@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux