I am reporting this again (revised), since the last time I reported it I only got a "can't reproduce" response (perhaps the report below of a similar problem with renaming columns suggests that my problem is not an isolated one).
Using pgAdminIII 1.16 (Windows 7 64-bit): Renaming a table by right clicking on the table icon, selecting Properties... on the contextual menu and then editing the Name field on the Properties tab and then clicking on the OK button will consistently cause a freeze up or crash of the pgAdminIII app. I have found this problem on two different sites that I am accessing using the built in Windows Terminal Services RDP client. I have to then force quit the app using the Task Manager. If I do it "locally" (on my local computer against a server running on the same machine) then the result is not a freeze up, but a Windows system dialog offering me the options of "Check online for a solution and close the program" or "Close the program" either of which forces an exit of pgAdminIII. In either the case of remote access or locally, when I relaunch pgAdminIII I have noticed that the rename successfully occurred. Gary Giumarra DealerBuilt-Lightyear Dealer Technologies, LLC. Senior Accounting Developer ________________________________ From: Dave Page <dp...@pgadmin.org> To: Federico Verponziani <frc....@gmail.com> Cc: pgadmin-support@postgresql.org; Sachin Srivastava <sachin.srivast...@enterprisedb.com> Sent: Wed, October 31, 2012 9:15:27 AM Subject: Re: [pgadmin-support] Crash after renaming columns Hi Sachin Can you take a quick look at this please? Thanks. On Wed, Oct 31, 2012 at 4:11 PM, Federico Verponziani <frc....@gmail.com> wrote: > Hi all, > I am using PgAdmin v.1.16.0 in both Windows 7 32 and 64 bit and I > encountered this error. > After I try to rename a column from the column properties, pgAdmin crashes. > It crashed either on a Windows 7 32 bit pc working on a Postgres db v.9.1 > installed on a Ubuntu server machine and on a Windows 7 64 bit pc working on > a Postgres db v.9.2 installed locally. > I've tried to search if it was a known bug but I've not found anything. > Sorry for any inconvenience, it's the first bug I report. > > Federico -- 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@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
