agora inbox for postgres@postgres.berkeley.edu
help / color / mirror / Atom feedFrom: Paul M. Aoki <aoki@postgres.Berkeley.EDU>
To: Vincent Schenkelaars <schenkel@cs.few.eur.nl>
Cc: postgres@postgres.Berkeley.EDU
Subject: Re: postgres 4.2 beta installation
Date: Tue, 12 Apr 94 10:42:34 -0700
Message-ID: <199404121742.KAA16548@faerie.CS.Berkeley.EDU> (raw)
In-Reply-To: <9404121217.AA26461@argon.cs.few.eur.nl>
Vincent Schenkelaars <schenkel@cs.few.eur.nl> 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 the same problems. I'm runiing on a Sparc IPC running SunOS 4.1.3
> looks like there is something strange with the SunOS port.
or your environment, or the polarity of the neutron flow in your
IPC, or <insert random factor here>... it's hard to tell -- other
outside people have successfully installed it. i start up postmaster
on sparcs using $PATH all the time.
(i trust you guys aren't deviating from the instructions in some
obvious way, like using gcc or something. i guarantee that gcc
won't work for this on any RISC machine.)
> I noticed that there is no longer a reference to PGHOST and PGDATA
> envirinment variablkes in the instalation guide. Are these no longer needed?
the short answer:
they are both documented in the reference manual.
the long answer:
they both exist and have the same meaning. i have no idea why
they aren't mentioned in the installation notes, but now that i
think about it, they shouldn't be necessary if you correctly set
POSTGRESDIR in your Makefile.global, because this sets the right
compiled-in path. if you then move things around you will have
to set PGDATA; likewise, if you used to use 4.1 and habitually
set PGDATA to the location of the 4.1 data, you will have to
unset it or change it.
--
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, schenkel@cs.few.eur.nl
Subject: Re: postgres 4.2 beta installation
In-Reply-To: <199404121742.KAA16548@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