pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dave Cramer <pg@fastcrypt.com>
To: Richard Huxton <dev@archonet.com>
Cc: amrit@health2.moph.go.th, PGsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Increasing RAM for more than 4 Gb. using postgresql
Date: Wed, 19 Jan 2005 08:41:29 -0500
Message-ID: <41EE6389.8020303@fastcrypt.com> (raw)
In-Reply-To: <41EE4091.9040902@archonet.com>
References: <1105501768.41e49e484d779@webmail.moph.go.th>
	<Pine.LNX.4.58.0501122343160.6728@linuxworld.com.au>
	<cs67u3$kp7$1@news.hub.org>
	<200501160944.47511.josh@agliodbs.com>
	<csgtff$2lae$1@news.hub.org>
	<011901c4fd5e$4b465470$63070080@freedom>
	<1106059106.41ed1f6296062@webmail.moph.go.th>
	<41EE4091.9040902@archonet.com>

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@health2.moph.go.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




view thread (23+ messages)

Message-ID: <41EE6389.8020303@fastcrypt.com>
Permalink:  ../41EE6389.8020303@fastcrypt.com/
Also on:    postgresql.org/message-id/41EE6389.8020303@fastcrypt.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: pg@fastcrypt.com, dev@archonet.com
  Subject: Re: Increasing RAM for more than 4 Gb. using postgresql
  In-Reply-To: <41EE6389.8020303@fastcrypt.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox