Re: pgAdmin III v1.10.5. Unable to Delete/Drop a server
| От | Dave Page |
|---|---|
| Тема | Re: pgAdmin III v1.10.5. Unable to Delete/Drop a server |
| Дата | |
| Msg-id | AANLkTikuBUN=cW4nGsT31c9L4qt+3Ya9Chw5eZnQd7Fw@mail.gmail.com обсуждение исходный текст |
| Ответ на | pgAdmin III v1.10.5. Unable to Delete/Drop a server (John Skillings <jskillings07@gmail.com>) |
| Ответы |
Re: pgAdmin III v1.10.5. Unable to Delete/Drop a server
|
| Список | pgadmin-support |
On Fri, Dec 31, 2010 at 12:44 AM, John Skillings <jskillings07@gmail.com> wrote: > Hi All, > > Earlier today, I upgraded my postgres database from 8.3 to 8.4.6. My > development platform is Win XP SP3. > > Prior to installing 8.4.6, I removed all the files connected with 8.3. > > Install went ok. However, when I start new pgAdmin III, I still find the > servers from the previous version. I am unable to delete/drop them. I can > delete/drop, but when I restart the pgAdmin III, the servers are still > there. > > A similar behaviour was reported previously at: > > http://archives.postgresql.org/pgsql-novice/2010-09/msg00187.php > > Is there some hidden pgAdmin III configuration that stores the configuration > information? If so, where I can I find it. Sounds like you just deleted 8.3 instead of properly uninstalling it, and pgAdmin is still finding all the registry keys for it. Is that the case? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgadmin-support по дате отправления: