BTW what is show below was done on
a different machine where postgres is
installed in a user directory..
Just to rule out confusion I had earlier
I deleted bin lib include in the user
home directory and reinstall it under
/usr/local/pgsql and the problem still
remains namely I have to supply extra -o
to make it work.
On Wed, Feb 21, 2001 at 11:43:46PM -0500, newsreader@mediaone.net wrote:
> Thank you. Look what I get..
> ------------------
> $ pg_ctl start -o "-F -S 2048"
> postmaster successfully started up.
> $ usage: /home/newsreader/pgsql/bin/postmaster [options]
> -B nbufs set number of shared buffers
> -D datadir set data directory
> -S silent mode (disassociate from tty)
> -a system use this authentication system
> -b backend use a specific backend server executable
> -d [1-5] set debugging level
> -i listen on TCP/IP sockets as well as Unix domain socket
> -N nprocs set max number of backends (1..1024, default 32)
> -n don't reinitialize shared memory after abnormal exit
> -o option pass 'option' to each backend servers
> -p port specify port for postmaster to listen on
> -s send SIGSTOP to all backend servers if one dies
> ---------------------
>
>
> I've found that
> pg_ctl -o "-o -F -S 2048" start
> works as well as
> pg_ctl start -o "-o -F -S 2048"
>
> ------
> If you read man page of pg_ctl you will see that
> it is telling you wrong
>
>
>
>
>
> On Wed, Feb 21, 2001 at 11:29:30PM -0500, Tom Lane wrote:
> > newsreader@mediaone.net writes:
> > > pg_ctl is completely not working for me. I do
> > > $ pg_ctl -o "-F -S 2048" start
> > > and it keeps telling me I'm not doing it right.
> >
> > Indeed, you are not. Try
> > pg_ctl start -o "-F -S 2048"
> >
> > regards, tom lane
