Re: BUG #13839: command line restart server fail

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Ali Raza <alirazaidi(at)hotmail(dot)com>
Cc: "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13839: command line restart server fail
Date: 2016-01-01 07:39:40
Message-ID: CAB7nPqQkTmi62qYJD3tBaSQTTiDV6ED4C-CoLq27vDr8Tc5xwA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Dec 31, 2015 at 3:20 AM, Ali Raza <alirazaidi(at)hotmail(dot)com> wrote:
> This happens when localhost is used in pg_hba.conf and stated command stuck
> at last line until I press enter.

(Please avoid top-posting, that is annoying for everybody here and it
breaks the logic of the thread...)
What kind of client are you using to connect to the Postgres server
after starting it? Npgsql? What is the failure you are seeing and what
is the command you are mentioning? Are you getting a connection
failure caused by a missing entry in pg_hba.conf?

> When I see windows services postgres service is stopped.
> Further more trying to connect with pgAdmin I receive connectivity error.

What do the contents of your logs show you? First where are things
logged out? For example what is the setting value for log_destination?
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Kouhei Sutou 2016-01-01 09:14:28 Re: BUG #13840: pg_dump generates unloadable SQL when third party string type index option is used
Previous Message kou 2015-12-31 15:35:22 BUG #13840: pg_dump generates unloadable SQL when third party string type index option is used