Re: Database access error after upgrade 7.1.2 -> 7.1.3
От | postgresql |
---|---|
Тема | Re: Database access error after upgrade 7.1.2 -> 7.1.3 |
Дата | |
Msg-id | 200110101221.f9ACLhn64474@postgresql.org обсуждение исходный текст |
Ответ на | Database access error after upgrade 7.1.2 -> 7.1.3 (Steve Frampton <frampton@LinuxNinja.com>) |
Список | pgsql-admin |
What happens when you update from your data dump (pg_dumpall) that you do to backup your data? You did do a pg_dumpall before you did the update? I don't think it is required to upgrade from 7.1.2 to 7.1.3. What happens when you run version 7.1.2 and access the data? /home2/pgsql /home2/pgsql-7.1.2/postmaster -D /home2/pgsql/data -i & This should run your old version of posgresql, then you could run pg_dump for the database ( /home2/pgsql /home2/pgsql-7.1.2/pg_dump **database here** > backup.out) and use this to populate your new setup. I see that from your startup you are not saving the output of postgres to a file so there is no way to look at the log. Ted -----Original Message----- From: Steve Frampton <frampton@linuxninja.com> To: <pgsql-admin@postgresql.org> Date: Wed, 10 Oct 2001 04:42:19 -0400 (EDT) Subject: [ADMIN] Database access error after upgrade 7.1.2 -> 7.1.3 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello: > > I just moved a database server from 7.1.2 to 7.1.3. After looking in > the > ChangeLog and not seeing anything that would seem to indicate any DB > structural changes, I did the upgrade as follows: > > pg_ctl stop -D /home2/pgsql/data -w -m smart > mv /home2/pgsql /home2/pgsql-7.1.2 > mkdir /home2/pgsql && cd /home2/pgsql && cp -R /home2/pgsql/data && > chown postgres:postgres data > > (Built and installed 7.1.3) > > /home2/pgsql/bin/postmaster -D /home2/pgsql/data -i & > > No errors were reported, and I can access my user created databases. > However, if I try to connect to template0, I get the following error > message: > > psql: FATAL 1: Database "template0" is not currently accepting > connections > > (Again, user created databases, as well as template1, can be accessed > normally.) > > Is there a solution for this? If not, my boss is wondering if suicide > is > a viable alternative. > > Thanks... > > - ---------------< LINUX: The choice of a GNU generation. > >------------- > Steve Frampton <frampton@LinuxNinja.com> http://www.LinuxNinja.com > GNU Privacy Guard ID: D055EBC5 (see http://www.gnupg.org for details) > GNU-PG Fingerprint: EEFB F03D 29B6 07E8 AF73 EF6A 9A72 F1F5 D055 EBC5 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.0 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE7xAnvmnLx9dBV68URAgHvAJ4iowIin8sz4n6WhTtWcTHW dpHLZwCfYKb/ > UoXfLSLQO6FxYnzyKmPMdXI= > =HHAV > -----END PGP SIGNATURE----- > > > ---------------------------(end of > broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to > majordomo@postgresql.org
В списке pgsql-admin по дате отправления: