Ozan Kahramanogullari <ozan.kah@gmail.com> writes:
> I am attaching the output of "ps auxww". I am not able to make any sense of
> it, sorry! Maybe you can?
I only see one postmaster:
postgres 70 0.0 0.1 4511528 17908 ?? Ss 11:20AM 0:00.18 /Library/PostgreSQL/10/bin/postmaster
-D/Library/PostgreSQL/10/data
though it's got the usual collection of child processes:
postgres 211 0.0 0.0 4519444 1708 ?? Ss 11:20AM 0:00.00 postgres: bgworker: logical replication
launcher
postgres 209 0.0 0.0 4374376 1120 ?? Ss 11:20AM 0:00.48 postgres: stats collector process
postgres 208 0.0 0.0 4519444 2548 ?? Ss 11:20AM 0:00.15 postgres: autovacuum launcher process
postgres 207 0.0 0.0 4511252 5188 ?? Ss 11:20AM 0:00.04 postgres: wal writer process
postgres 206 0.0 0.0 4511252 2292 ?? Ss 11:20AM 0:00.05 postgres: writer process
postgres 205 0.0 0.0 4511252 2688 ?? Ss 11:20AM 0:00.01 postgres: checkpointer process
postgres 202 0.0 0.0 4366184 828 ?? Ss 11:20AM 0:00.00 postgres: logger process
and here's your psql and associated backend process:
root 1011 0.0 0.0 4299336 5720 s000 S+ 12:41PM 0:00.03 psql -U postgres
postgres 1012 0.0 0.0 4511640 2968 ?? Ss 12:41PM 0:00.00 postgres: postgres postgres [local] idle
So that all looks pretty normal, and shoots down my idea about two local
postmasters. That leaves the remote-connection idea. What do you get
from "nslookup localhost" on the command line? What happens if you
write "psql -h 127.0.0.1" instead of writing "psql -h localhost"?
regards, tom lane