This is a discussion on Re: "template1 does not exist" while installing 8.0RC5 on RH9 within the pgsql Admins forums, part of the PostgreSQL category; --> (red face) It seems I might possibly have neglected to kill the postmaster from 7.4 before installing 8.0. It ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| (red face) It seems I might possibly have neglected to kill the postmaster from 7.4 before installing 8.0. It is amazing how much better things work with the 8.0 postmaster. -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Monday, January 17, 2005 4:12 PM To: Rick Schumeyer Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] "template1 does not exist" while installing 8.0RC5 on RH9 "Rick Schumeyer" <rschumeyer@ieee.org> writes: > Everything looks good, even the "initdb" command, which reports > everything as ok. > But the "createdb test" command fails, with error > 'database "template1" does not exist' initdb executes half a dozen reconnections to template1 after the initial bootstrap, so it's real hard to see how a broken pg_database entry wouldn't have caused a failure during initdb. I'm wondering if maybe your createdb command is connecting to a different postmaster than you think it is. Check environment variables, path, etc. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |
| ||||
| "Rick Schumeyer" <rschumeyer@ieee.org> writes: > (red face) It seems I might possibly have neglected to kill the > postmaster from 7.4 before installing 8.0. Ooops ;-). If you didn't already, I'd suggest wiping and re-initdb'ing the PGDATA area. It's possible that the 7.4 postmaster corrupted things before you killed it. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |