when i start the postgres, it creates the follwoing processes for postgres:
1 S jsbali 4034 4033 0 76 0 - 2489 - 15:41 pts/2 00:00:00 postgres: logger process
1 S jsbali 4036 4033 0 75 0 - 5042 - 15:41 pts/2 00:00:00 postgres: writer process
1 S jsbali 4037 4033 0 76 0 - 2739 - 15:41 pts/2 00:00:00 postgres: stats buffer process
1 S jsbali 4038 4037 0 83 0 - 2547 - 15:41 pts/2 00:00:00 postgres: stats collector process
and gives the follwoing error
LOG: could not bind IPv4 socket: Address already in use
HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
At this point I would have no option but to kill -INT 4033. I do a ps -elf | grep jsbali again after this kill and i have nothing for postgres running. Good enough.
Then i try to start postgres again and it gives me the same error:
LOG: could not bind IPv4 socket: Address already in use
HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
It ends up being a cyclic problem.
Don't know how to get rid of it now.
Thanks,
Jas
On 10/11/06, Tom Lane <
tgl@xxxxxxxxxxxxx> wrote:
"J S B" < jsbali@xxxxxxxxx> writes:
> There was some problem with postmaster.pid file, so i just removed it.
Without bothering to stop the old postmaster first, I take it.
At this point your best bet is to find out the PID of the old postmaster
with "ps" and then kill it with "kill -INT <pid>". I suspect you've
also been sloppy about which userid you've been starting the postmaster
under ... you have to be consistent about that.
regards, tom lane
