Re: Upgrading Database: need to dump and restore?

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 12:23:23
Message-ID: h08ebo$u19$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.
""Grzegorz Jaskiewicz"" <gryzman(at)gmail(dot)com> wrote in message
news:2f4958ff0906040518l190af73dpff180755d567f3a8(at)mail(dot)gmail(dot)com(dot)(dot)(dot)
On Thu, Jun 4, 2009 at 1:07 PM, Carlos Oliva <carlos(at)pbsinet(dot)com> wrote:
> Thanks again Grzgorz for your expedicious reply. Would anything else
> change
> in the database for a table once it ceases to be updated? We have several
> tables for which a number of records is inserted and never again
> updated --
> data is never updated, deleted, or inserted again. We are moving these
> tables into their own tablespace and getting some kind of snapshot copy of
> these tables. We were thinking that we can restore them in the future
> without having to back them up several times.

Well, if you do pg_dump - that data will be there.
If you do copy of data directory, that isn't going to work, unless you
put db in proper state.
if you do that, you need to copy pg_xlog directory with it.

So you have to specify which backup strategy you are going to use.

--
GJ

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Leif B. Kristensen 2009-06-04 12:27:56 Re: Plpgsql functions with output parameters
Previous Message Geoffrey 2009-06-04 12:18:40 Re: warm standby with WAL shipping