Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 616938 - dev-db/postgresql-9.6.2-r1: doesn't listen on socket
Summary: dev-db/postgresql-9.6.2-r1: doesn't listen on socket
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: PgSQL Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-29 06:34 UTC by François Valenduc
Modified: 2017-05-13 06:26 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description François Valenduc 2017-04-29 06:34:13 UTC
Everything is explained in the subject. When I upgraded to postgresql 9.6.2-r1, I noticed that it didn't listen to socket connection. So I am forced to use psql -h locahost -U postgres instead of psql -U postgres to connect. Downgrading to postgresql-9.6.2 solved the problem, and I didn't change any configuration file.

Can somebody explains what's happening ?
Thanks in advance.

Reproducible: Always
Comment 1 Aaron W. Swenson gentoo-dev 2017-05-12 13:12:07 UTC
(In reply to François Valenduc from comment #0)
> Everything is explained in the subject. When I upgraded to postgresql
> 9.6.2-r1, I noticed that it didn't listen to socket connection. So I am
> forced to use psql -h locahost -U postgres instead of psql -U postgres to
> connect. Downgrading to postgresql-9.6.2 solved the problem, and I didn't
> change any configuration file.
> 
> Can somebody explains what's happening ?
> Thanks in advance.
> 
> Reproducible: Always

It is working for me on three different machines without any modifications. Just emerge and go.

Verify that both /etc/conf.d/postgresql-9.6 and /etc/init.d/postgresql-9.6 are updated. You should see PG_SOCKET_DIRECTORIES="/run/postgresql" in the conf.d/postgresql-9.6.
Comment 2 François Valenduc 2017-05-13 06:26:39 UTC
It was indeed a problem with the update of the configuration file. Now it works correctly. Sorry for the noise.