Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #2118: could not connect to server
- From: zhuge xiao <xiao(dot)zhuge(at)hhstech(dot)cn>
- To: tgl(at)sss(dot)pgh(dot)pa(dot)us, evrim(at)commandprompt(dot)com, pgsql-admin(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org, smarlowe(at)g2switchworks(dot)com
- Subject: Re: BUG #2118: could not connect to server
- Date: Fri, 23 Dec 2005 15:25:16 +0800
- Message-id: <43ABA65C.1080101@hhstech.cn> <text/plain>
Tom Lane, I have read the email you mailed me. And I have SELinux enabled in permissive mode and the testlibpq program can run. I am very happy. In the future, I will use the PostgreSQL and give up the MySQL and other databases. I think the PostgreSQL is better than the others. Thank you very much. zhuge xiao <zhuge(at)Rinaix(dot)cn> Tom Lane wrote:
"zhuge xiao" <zhuge(at)Rinaix(dot)cn> writes:could not connect to server: Permission denied Is the server running locally and accepting connections on Unix domain socket "/tmp/.s.PGSQL.5432"?"Permission denied" indicates a file permissions problem. Check the permissions on /tmp and on the socket file itself. If you have SELinux enabled in enforcing mode, you might also have a SELinux policy problem --- is your selinux-policy package up to date? regards, tom lane
- Prev by Date: Re: BUG #2118: could not connect to server [From zhuge xiao <zhuge(at)Rinaix(dot)cn>]
- Next by Date: BUG #2123: join between stored procedures
- Previous by thread: Re: BUG #2118: could not connect to server
- Next by thread: BUG #2119: FOREIGN KEY ON DELETE RESTRICT
- Indexes: