Jonel Rienton wrote:
you know what does work, if you issue the pg_ctl stop with /usr/local/
pgsql/data2 as the argument for -D
pg_ctl -D /usr/local/pgsql/data2 stop
Yes that does work as it should. However as Tom Lane pointed out the
problem is that pg_ctl can't parse the postgresql.conf so if y
you know what does work, if you issue the pg_ctl stop with /usr/local/
pgsql/data2 as the argument for -D
pg_ctl -D /usr/local/pgsql/data2 stop
odd tho.
On May 6, 2005, at 3:36 PM, Joshua D. Drake wrote:
Jonel Rienton wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
your data directory points
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> data_directory = '/usr/local/pgsql/data2' # use data in
> -bash-3.00$ bin/pg_ctl -D /usr/local/pgsql/etc stop
Fixing this would seem to require teaching pg_ctl how to parse the
postgresql.conf file, which might be worth doing but it's
I just tried the same setup as yours, and it worked fine, i was able
to start and stop the instance.
could it be that the process didn't start at all when you started it?
regards,
-
Jonel Rienton
http://homepage.mac.com/jrienton
Software Developer, *nix Advocate
On May 6, 2005, at 3:36 PM, J
Jonel Rienton wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
your data directory points to /usr/local/pgsql/data2 and you've
started it with -D /usr/local/pgsql/etc
might be something to look at
In version 8 you can specify the location of the data_directory with the
data_directory option
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
your data directory points to /usr/local/pgsql/data2 and you've
started it with -D /usr/local/pgsql/etc
might be something to look at
regards,
- -
Jonel Rienton
http://homepage.mac.com/jrienton
Software Developer, *nix Advocate
On May 6, 200
PostgreSQL 8.0.2 - Fedora 3
data_directory = '/usr/local/pgsql/data2' # use data in
hba_file = '/usr/local/pgsql/etc/pg_hba.conf' # the host-based #
ident_file = 'ConfigDir/pg_ident.conf' # the IDENT configuration file
external_pid_file = '/tmp/foo.pid' # write an ext
Hello,
I've noticed a bug if pg_ctl. If you do the following:
pg_ctl -w -D $PGSQL/data -o '-p 1' start;
The pg_ctl script will loop doing a 'psql -l' to connect to the postmaster
process on port 5432 (but postmaster is using 1 in this case). The
pg_ctl script should take the port number
