From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | amrit(at)health2(dot)moph(dot)go(dot)th, PGsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Increasing RAM for more than 4 Gb. using postgresql |
Date: | 2005-01-19 13:41:29 |
Message-ID: | 41EE6389.8020303@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
You can *not* go from any major release to another major release using
any kind of file backup. Please use pg_dump.
Additionally there are known issues dumping and restoring from 7.3 ->
7.4 if you use the default copy command. Use the pg_dump --inserts option.
I would still tar the directory just in case you *have* to fall back to
7.3 for some reason (Better safe than sorry )
Dave
Richard Huxton wrote:
> amrit(at)health2(dot)moph(dot)go(dot)th wrote:
>
>> I would like to upgrade both OS kernel and PGsql version , so in my
>> opinion the
>> best way to handle it is to *backup* the data in .tar
>
>
> Just remember if you're going from 7.3.2 => 7.4.x or 8.0 then you'll
> need to use pg_dump not just tar up the directories. If you do use
> tar, remember to backup *all* the directories.
>
> --
> Richard Huxton
> Archonet Ltd
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if
> your
> joining column's datatypes do not match
>
>
--
Dave Cramer
http://www.postgresintl.com
519 939 0336
ICQ#14675561
From | Date | Subject | |
---|---|---|---|
Next Message | Alan Stange | 2005-01-19 13:51:56 | Re: Swapping on Solaris |
Previous Message | Richard Huxton | 2005-01-19 11:12:17 | Re: Increasing RAM for more than 4 Gb. using postgresql |