agora inbox for postgres@postgres.berkeley.edu  
help / color / mirror / Atom feed
From: Paul M. Aoki <aoki@postgres.Berkeley.EDU>
To: jsrobin@afterlife.ncsc.mil
Cc: postgres@postgres.Berkeley.EDU
Subject: Re: postgres 4.2 beta installation
Date: Fri, 08 Apr 94 17:44:36 -0700
Message-ID: <199404090044.RAA12526@faerie.CS.Berkeley.EDU> (raw)
In-Reply-To: <199404082306.TAA21800@afterlife.ncsc.mil>

"John S. Robinson" <jsrobin@afterlife.ncsc.mil> writes:
> In each case, initdb completes successfully. In each case when
> 	postmaster is run it core dumps. In each case if I run postmaster
> 	by specifying its full path length, postmaster will run. 

i have no idea what executables you have where in your $PATH, but
the fact that an absolute pathname for postmaster works makes me
wonder..

> In most cases when I attempt to run createdb, I am given an error
> 	message stating that the database model template1 does not exist
> 	(even though initdb completed without complaint).

this indicates that the postmaster is looking in the wrong place 
for its database directory.  this is not detected until runtime.
for example:

faerie:postgres (11)> setenv PGDATA /no/such/directory
faerie:postgres (12)> postmaster&
[1] 12232
faerie:postgres (13)> monitor template1
FATAL 1:Apr  8 16:41:19:database template1 does not exist, bailing out...
faerie:postgres (14)> 

if your environment is such that initdb and the postmaster are working 
in different places (for example, you set PGDATA in one shell and set 
it to something else in another; or if you ran initdb and *then* set
PGDATA) you have an obvious problem.

untangling environment dependencies and inconsistencies is so much
fun.  someone else is having an awful time with the same kind of hair;
the output from regression plainly indicate that the 4.2 regression 
tests are being run on a set of 4.1 binaries/databases (4.1 is also 
installed).  for example, it doesn't understand the new define 
{function,operator, aggregate} syntax or the new array syntax, and 
gives the *exact same* error messages that my copy of 4.1 gives when
presented with the same syntax..  you would like to believe that it's
easy to figure out what's going on in this kind of case, but sometimes 
it isn't..
--
  Paul M. Aoki  |  CS Div., Dept. of EECS, UCB  |  aoki@postgres.Berkeley.EDU
                |  Berkeley, CA 94720           |  ...!uunet!ucbvax!aoki




reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: postgres@postgres.berkeley.edu
  Cc: aoki@postgres.Berkeley.EDU, jsrobin@afterlife.ncsc.mil
  Subject: Re: postgres 4.2 beta installation
  In-Reply-To: <199404090044.RAA12526@faerie.CS.Berkeley.EDU>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox