Re: BUG #6678: error in connecting to Pgadmin

From: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
To: renjibabu(at)ymail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6678: error in connecting to Pgadmin
Date: 2012-06-08 13:56:13
Message-ID: 4FD2047D.8080304@ringerc.id.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 06/08/2012 05:08 PM, renjibabu(at)ymail(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6678
> Logged by: Renji
> Email address: renjibabu(at)ymail(dot)com
> PostgreSQL version: 9.1.0

There's your first problem. Why use such an old release? If you're
reporting a bug, you should test with the latest version.

> Operating system: windows 7

Windows 7 **WHAT**?

"Windows 7 Professional Service Pack 1 x64" ?

Also, is the machine joined to a corporate domain?

Is there a virus scanner or other "security" software installed?

> But when I shutdown and tried to start the service again, it is showing as
> the service is connected and if I try to connect to database it's giving
> the following message:

If you do start->run (or hold the windows key and press the R key) then
enter "services.msc", does the PostgreSQL service show up as started there?

If you examine the PostgreSQL error logs in the pg_log directory under
the PostgreSQL data directory (by default, inside the PostgreSQL program
install directory in program files) are there any messages there? If
there are, paste them.

Examine the windows Event Viewer (you can find it in the Start Menu by
searching for Event Viewer) do you see anything related to the
PostgreSQL service? Search for "postgres".

In the process list in Proces Explorer or Task Manager, does the
"postgres.exe" process appear? There should be several of them.

--
Craig Ringer

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Craig Ringer 2012-06-08 14:03:10 Re: BUG #6679: Can't connect via JDBC Driver
Previous Message Andres Freund 2012-06-08 11:40:45 Re: BUG #6661: out-of-order XID insertion in KnownAssignedXids