Search Postgresql Archives

upgrading from 8.0 rc5

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

To: "pgsql-general@xxxxxxxxxxxxxx" <pgsql-general@xxxxxxxxxxxxxx>
Subject: upgrading from 8.0 rc5
From: snacktime <snacktime@xxxxxxxxx>
Date: Mon, 11 Jul 2005 10:58:00 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=dD3TRSXU0hYo6JyxAVnmk9hQenCDeGbhWd1yYOapvqvEW+UfJvcjqItr8uWUV+RQIT05DV0RyGrW3toe0y/ZTjsC2bh3oKrqn3CbG1zYJ+DKuk5Yb9fKVERjXNMoOjJ4xDNHXiK3TA05jIHb8ThMaPdI/ze60nHQfpmc0MWqjus=
Reply-to: snacktime <snacktime@xxxxxxxxx>
Sender: pgsql-general-owner@xxxxxxxxxxxxxx

Do I need to do a full dump/restore when migrating from 8.0 rc5 to the
latest 8.0.3?

Chris

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

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

Follow-Ups:
- Re: upgrading from 8.0 rc5
  - From: Tom Lane
- Re: upgrading from 8.0 rc5
  - From: Michael Fuhr

Prev by Date: strange problem with pl/pgsql function caching of bad values
Next by Date: Re: PostgreSQL Hosting
Previous by thread: strange problem with pl/pgsql function caching of bad values
Next by thread: Re: upgrading from 8.0 rc5
Index(es):
- Date
- Thread

[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