Re: BUG #6627: Error while launching pgAdmin III

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Pooja Khobragade" <Pooja_Khobragade(at)persistent(dot)co(dot)in>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #6627: Error while launching pgAdmin III
Date: 2012-05-07 16:54:22
Message-ID: 4FA7B7EE020000250004791D@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Pooja Khobragade <Pooja_Khobragade(at)persistent(dot)co(dot)in> wrote:

> I guess I get this error because there are two versions of
> postgreSQL installed on the same machine.

It sounds like that may be part of the problem, or an improper or
incomplete attempt at an update to a new major version.

On the other hand, there is definitely more to the problem than
running two versions on the same machine. In our shop, we do that
all the time without problems. It can work fine as long as you
manage it correctly.

Have you performed an upgrade to a new major version of PostgreSQL
lately? Have you ever moved or copied PostgreSQL executable files
from one location to another?

-Kevin

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message clay 2012-05-07 18:52:08 BUG #6633: PL/Python build does not honor PYTHON on Mac OS X
Previous Message tom Tom 2012-05-07 16:31:40 Re: BUG #6629: Creating a gist index fails with "too many LWLocks taken"