From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Ed L(dot)" <pggeneral(at)bluepolka(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: 7.3 pg_ctl anomaly |
Date: | 2002-12-04 14:34:05 |
Message-ID: | 13936.1039012445@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Ed L." <pggeneral(at)bluepolka(dot)net> writes:
> When I run this command in 7.3,
> pg_ctl -w -o "-p 15432" start
> it successfully starts the database, but the -w flag doesn't seem to
> notice the successful start and continues to wait until finally
> saying "postmaster does not start" and giving up.
I believe the issue is that pg_ctl doesn't understand that you're
starting the postmaster on a nonstandard port. Its method of detecting
postmaster startup is to try to log in with psql, so if it's trying
the wrong port this is exactly what will happen.
I have not tried it, but I think it'd work to do this instead:
export PGPORT=15432
pg_ctl start
Making your example work as given would mean teaching the pg_ctl
script to parse postmaster options, which seems like way more
trouble than it's worth ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew Gabeler-Lee | 2002-12-04 15:00:30 | Re: 7.3 no longer using indexes for LIKE queries |
Previous Message | Diogo Biazus | 2002-12-04 14:30:20 | mod_auth_pgsql |