Submitted by Ray (not verified) on Fri, 2008-02-15 05:20.
A dump/restore is normal practice when doing major-version upgrades of PostgreSQL - and yes, 8.2 -> 8.3 is a major version! This is flagged pretty clearly both in the release notes, under the heading "Migration to version 8.3" (near the top), and in the "upgrading" part of the installation guide.
Major-version upgrades are something you'd plan pretty carefully with any DBMS, scheduling downtime if necessary, or quite possibly (and painlessly) using Slony (PG's replication system) to do the data transfer for you if downtime is an issue. This is one of the scenarios which the Slony designers had in mind when creating it, and it works very well. If you do go down the dump-reload route, don't use the --column-inserts option either if the data set is large, as this is pretty slow; instead allow pg_dump to default to generating COPY commands for reloading data, which is really fast.
Regarding the PgAdmin connection problem, did you add a line to pg_hba.conf to allow the client machine to connect? Out of the box, PostgreSQL disallows connections from remote machines until you explicitly enable them by editing this file, which is very well documented via comments.
Finally, if you're new to PostgreSQL, it's well worth subscribing to the pgsql-general mailing list (see the "Community" section of the website) - the support and help that'll you'll get there is *unbelievably* good.
»
Reply
Search
Windows for Intel Macs
Todd Ogasawara's Windows for Intel Macs ($7.99USD published by O'Reilly Media) is for Intel Mac users running Bootcamp or Parallels who want to learn more about running Microsoft Windows XP on Mac. It also provides specific tips and hints for using Parallels Desktop for Mac.
A dump/restore is normal
A dump/restore is normal practice when doing major-version upgrades of PostgreSQL - and yes, 8.2 -> 8.3 is a major version! This is flagged pretty clearly both in the release notes, under the heading "Migration to version 8.3" (near the top), and in the "upgrading" part of the installation guide.
Major-version upgrades are something you'd plan pretty carefully with any DBMS, scheduling downtime if necessary, or quite possibly (and painlessly) using Slony (PG's replication system) to do the data transfer for you if downtime is an issue. This is one of the scenarios which the Slony designers had in mind when creating it, and it works very well. If you do go down the dump-reload route, don't use the --column-inserts option either if the data set is large, as this is pretty slow; instead allow pg_dump to default to generating COPY commands for reloading data, which is really fast.
Regarding the PgAdmin connection problem, did you add a line to pg_hba.conf to allow the client machine to connect? Out of the box, PostgreSQL disallows connections from remote machines until you explicitly enable them by editing this file, which is very well documented via comments.
Finally, if you're new to PostgreSQL, it's well worth subscribing to the pgsql-general mailing list (see the "Community" section of the website) - the support and help that'll you'll get there is *unbelievably* good.