Thread: Load DB - Conversion from 8.1.4 to 8.2.4
I will be converting from PostgreSQL 8.1.4 to 8.2.4. Is it OK to do the following command in order to load the new database after install?
pg_dump -h host1 –p 1234 dbname | psql -h host1 –p 56789 dbname
Remember that port 1234 is PostgreSQL 8.1.4 and port 5678 is PostgreSQL 8.2.4.
Thanks,
Lance Campbell
Project Manager/Software Architect
Web Services at Public Affairs
University of Illinois
217.333.0382
http://webservices.uiuc.edu
Campbell, Lance wrote: > > I will be converting from PostgreSQL 8.1.4 to 8.2.4. Is it OK to do > the following command in order to load the new database after install? > > pg_dump -h /host1/ –p 1234 /dbname/ | psql -h /host1 –p 56789/ /dbname/// > > Remember that port 1234 is PostgreSQL 8.1.4 and port 5678 is > PostgreSQL 8.2.4. > Should be fine, as long as you ensure that the pg_dump you use, is the one from your 8.2.4 installation, and not the 8.1.4 version. -- Tommy Gildseth DBA, Gruppe for databasedrift Universitetet i Oslo, USIT m: +47 45 86 38 50 t: +47 22 85 29 39
Tommy Gildseth wrote: > Campbell, Lance wrote: >> >> I will be converting from PostgreSQL 8.1.4 to 8.2.4. Is it OK to do >> the following command in order to load the new database after install? >> >> pg_dump -h /host1/ –p 1234 /dbname/ | psql -h /host1 –p 56789/ >> /dbname/// >> >> Remember that port 1234 is PostgreSQL 8.1.4 and port 5678 is >> PostgreSQL 8.2.4. >> > > Should be fine, as long as you ensure that the pg_dump you use, is the > one from your 8.2.4 installation, and not the 8.1.4 version. > > Two quick addendums: - pg_dump doesn't dump large objects. You should use the following if you use large objects. pg_dump -h /host1/ –p 1234 -Fc /dbname/ | pg_restore -h /host1 –p 56789/ /dbname/// - There might be some other issues with the upgrade. I've run into permissions issues, data types that were checked more strictly, and a couple broken primary keys in my days as an admin. I'm not saying you'll run into these, but if you can, do a dry run of a dump/restore so you can solve the problems up front. Peter
I was thinking about upgrading from 8.1.4 to 8.1.9. Then I will do the upgrade from 8.1.9 to 8.2.4. Is this a better approach? Thanks, Lance Campbell Project Manager/Software Architect Web Services at Public Affairs University of Illinois 217.333.0382 http://webservices.uiuc.edu -----Original Message----- From: Peter Koczan [mailto:pjkoczan@gmail.com] Sent: Tuesday, June 26, 2007 7:14 PM To: Tommy Gildseth Cc: Campbell, Lance; pgsql-admin@postgresql.org Subject: Re: [ADMIN] Load DB - Conversion from 8.1.4 to 8.2.4 Tommy Gildseth wrote: > Campbell, Lance wrote: >> >> I will be converting from PostgreSQL 8.1.4 to 8.2.4. Is it OK to do >> the following command in order to load the new database after install? >> >> pg_dump -h /host1/ -p 1234 /dbname/ | psql -h /host1 -p 56789/ >> /dbname/// >> >> Remember that port 1234 is PostgreSQL 8.1.4 and port 5678 is >> PostgreSQL 8.2.4. >> > > Should be fine, as long as you ensure that the pg_dump you use, is the > one from your 8.2.4 installation, and not the 8.1.4 version. > > Two quick addendums: - pg_dump doesn't dump large objects. You should use the following if you use large objects. pg_dump -h /host1/ -p 1234 -Fc /dbname/ | pg_restore -h /host1 -p 56789/ /dbname/// - There might be some other issues with the upgrade. I've run into permissions issues, data types that were checked more strictly, and a couple broken primary keys in my days as an admin. I'm not saying you'll run into these, but if you can, do a dry run of a dump/restore so you can solve the problems up front. Peter
"Campbell, Lance" <lance@uiuc.edu> writes: > I was thinking about upgrading from 8.1.4 to 8.1.9. Then I will do the > upgrade from 8.1.9 to 8.2.4. AFAIK there's no point to that. Just jump to 8.2 in one step. There are not any bug fixes in 8.1.9 that you'd not get from 8.2.x. regards, tom lane