Re: cannot remove some items from the server list after upgrade from postgres 8.x to 9.x

From: Doug Easterbrook <doug(at)artsman(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: cannot remove some items from the server list after upgrade from postgres 8.x to 9.x
Date: 2011-01-10 13:29:22
Message-ID: A8E40EB0-EE54-4F23-B21E-7C3A979F0E79@artsman.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

we do.

on windows, standard procedure on an upgrade is to:
a) dump the database
b) go to add/remove programs and remove the old server (it leaves the database 'data' around)
c) install the new server
d) restore the new database.

in all cases, I get 8.4 and 9.0 databases pointing to the same thing.

once we are sure the customer is running on the windows machine under 9.0, then we go back and delete 8.3 or 8.4 directory from the program files/postres directory.

I still cannot, at that time, delete the reference from pgadmin

on OSX, our procedure is similar:

a) dump the database
b) stop the server
c) uninstall the old one (leaves data directory)
d) install the new server
e) config and start the server
f) restore the database
g) test that it works, then remove the old data directory.

We do that for safety just in case we have to rollback and reinstall the earlier postgres version. Since the old data directory is there, being able to revert back if necessary has saved our bacon a couple of times.

thats how the postgres installer works. If pgadmin is testing the data directory for existance, then it should probably test some other directory like the bin directory to see if its a real installation.

there is probably also no reason to disallow deleting of a server for any reason. If I want to delete all the servers in the list, that should be a personal choice. I really like that it adds the new server on upgrade... but the old should be allowed to be deleted if I wish. thats the essence of the bug report... an old server that no longer exists cannot be deleted.

Doug Easterbrook
Arts Management Systems Ltd.
mailto:doug(at)artsman(dot)com
http://www.artsman.com
Phone (403) 536-1205 Fax (403) 536-1210

On Jan 10, 2011, at 6:11 AM, Dave Page wrote:

> On Mon, Jan 10, 2011 at 1:03 PM, Doug Easterbrook <doug(at)artsman(dot)com> wrote:
>> I've discovered that as we migrate a each of our customers from 8.4 to 9.x
>> of postgres, we see that the nubmer of servers always changes from only
>> Servers (1)
>> -> PostgreSQL 8.4 (localhost:5432)
>> to be two servers in the pgadmin list
>> Servers (2)
>> -> PostgreSQL 8.4 (localhost:5432)
>> -> PostgreSQL 9.0 (localhost:5432)
>>
>>
>> I've seen that before in earlier version upgrades, and it was easy enough to
>> delete one (or so I think).
>> now, once you have both of these in your list of servers, I find that you
>> can't delete a server by using right -click & delete/drop
>> I've inspected the postgres preferences and the information stays in the
>> preferences .
>>
>> When you delete them, it looks like they go away, but when you restart
>> pgadmin, the serve you just deleted comes back.
>
> You need to uninstall the old server. Otherwise, pgAdmin will
> re-detect it, and add it back to the list.
>
>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
> --
> Sent via pgadmin-support mailing list (pgadmin-support(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-support

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Dhiraj Chawla 2011-01-10 15:21:31 Re: [pgadmin-support] pgAdmin Crashes When Opening a *.sql File From Windows Explorer
Previous Message Russell L. Galyon 2011-01-10 13:19:50 Re: pgAdmin Crashes When Opening a *.sql File From Windows Explorer