Monday, February 18, 2008

upgrading to postgresql 8.3 in debian from 7.4

me:/home/me# pg_dropcluster 8.3 main --stop
me:/home/me# pg_upgradecluster 7.4 main
Checking for users and groups with the same name...
Creating new cluster (configuration: /etc/postgresql/8.3/main, data: /var/lib/postgresql/8.3/main)...
Moving configuration file /var/lib/postgresql/8.3/main/postgresql.conf to /etc/postgresql/8.3/main...
Moving configuration file /var/lib/postgresql/8.3/main/pg_hba.conf to /etc/postgresql/8.3/main...
Moving configuration file /var/lib/postgresql/8.3/main/pg_ident.conf to /etc/postgresql/8.3/main...
Configuring postgresql.conf to use port 5433...
Disabling connections to the old cluster during upgrade...
Disabling connections to the new cluster during upgrade...
Re-enabling connections to the old cluster...
Re-enabling connections to the new cluster...
Creating globals...
Fixing hardcoded library paths for stored procedures...
Upgrading database LTA_FIS...
Analyzing database LTA_FIS...
Fixing hardcoded library paths for stored procedures...
Upgrading database CTNControl...
Analyzing database CTNControl...
Fixing hardcoded library paths for stored procedures...
Upgrading database LTA_IDB...
Analyzing database LTA_IDB...
Fixing hardcoded library paths for stored procedures...
Upgrading database template1...
Analyzing database template1...
Copying old configuration files...
Copying old start.conf...
Stopping target cluster...
Stopping old cluster...
pg_ctl: postmaster does not shut down
Disabling automatic startup of old cluster...
Configuring old cluster to use a different port (5433)...
Starting target cluster on the original port...
WARNING: connection to the database failed, disabling startup checks:
psql: FATAL: the database system is shutting down

Success. Please check that the upgraded cluster works. If it does,
you can remove the old cluster with

pg_dropcluster 7.4 main
wustl@me:~/perlscripts$ ./startctn.pl
both the archive_agent and archive_server processes have started yay!
wustl@me:~/perlscripts$ 170162 DB specific error (PostgreSQL:(null)) in PG_Open
140162 Could not allocate connection handle. dbinit()/dblogin() failed in PG_Open
40192 Bad Database/Table [LTA_IDB/PatientLevel] in IDB_Open
Fatal error during startup
170162 DB specific error (PostgreSQL:(null)) in PG_Open
140162 Could not allocate connection handle. dbinit()/dblogin() failed in PG_Open
40172 Failed to open table ApplicationEntity in function DMAN_Open
bfff4 APP Failed during startup: Could not open control database
120172 DMAN Illegal handle passed to function DMAN_Close
Exiting