Thanks for the advice!!
I'll probably add those PGDATA variables to my startup script.
Also, is there a way to circumvent this error (of missing $PGDATA3)?
Otherwise I'll need to wait for a couple of months if I have to restart
the server.
The database in question, and the datpath, has not been
Ben Kim <[EMAIL PROTECTED]> writes:
> I'm starting it with something like the following, as root in /etc/init.d
> script.
> su pgsql -c "/usr/local/pgsql/bin/pg_ctl -D /usr/local/pgsql/data
> -p /usr/local/pgsql/bin/postmaster start"
> And pgsql has PGDATA3 defined in .cshrc.
su is
Many thanks for the advice.
I'm starting it with something like the following, as root in /etc/init.d
script.
su pgsql -c "/usr/local/pgsql/bin/pg_ctl -D /usr/local/pgsql/data
-p /usr/local/pgsql/bin/postmaster start"
And pgsql has PGDATA3 defined in .cshrc.
The PGDATA3 is not be
Ben Kim <[EMAIL PROTECTED]> writes:
> pgsql=# drop database mydb;
> ERROR: Postmaster environment variable 'PGDATA3' not set
> The database owner is pgsql, and if I echo $PGDATA3 as the owner, it
> returns a valid directory. Also, the datpath is correct.
You have $PGDATA3 set in your interactive
Dear list,
I'm using Postgresql 7.2 on Solaris.
I have this error message when I try to drop a database. I couldn't find a
mention anywhere on this error. Could someone advise how to circumvent
this error?
pgsql=# drop database mydb;
ERROR: Postmaster environment variable 'PGDATA3' not set
Th
