Rich Shepard wrote:
> What mode should PGDATA2/base or PGDATA have so I can create databases in
> it?
700 is the right permissions -- make sure that the postgres user is the
owner of the PGDATA2.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
On Sat, 27 Nov 1999, Lamar Owen wrote:
> 700 is the right permissions -- make sure that the postgres user is the
> owner of the PGDATA2.
Lamar,
Ah, ha! That must be the problem. The definition of PGLIB, PGDATA and
PGDATA2 are in *my* ~/.bash_profile. When I was logged in as postgres, I
set up
Rich Shepard wrote:
> On Sat, 27 Nov 1999, Lamar Owen wrote:
> > 700 is the right permissions -- make sure that the postgres user is the
> > owner of the PGDATA2.
> Ah, ha! That must be the problem. The definition of PGLIB, PGDATA and
> PGDATA2 are in *my* ~/.bash_profile. When I was logged
On Sat, 27 Nov 1999, Lamar Owen wrote:
Lamar,
> H.. Without any of the PostgreSQL envvars defined, on 6.5.3, I (as
> user lowen) can successfully create and destroy db's -- lowen has create
> database rights.
I think that I'm missing something very basic here, for I still cannot
create a
Rich Shepard wrote:
> I think that I'm missing something very basic here, for I still cannot
> create a db. As a user (with priviledges to create and destroy db's), I cd
> to PGDATA2 (in my case ~/accounting/paisley) and issue the command:
>
> createdb -D PGDATA2 test
> or
> cre
On Sat, 27 Nov 1999, Lamar Owen wrote:
> Who owns '/home/rshepard/accounting/paisley', rshepard or postgres? The
> postgres user needs to own both PGDATA and PGDATA2. Also, to call up
> the envvar in the shell like this, you need to call it as $PGDATA or
> ${PGDATA}.
It's embarrassing to app
