Re: Crash in pgadmin3 (Recent Files for postgresql.conf)

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: Crash in pgadmin3 (Recent Files for postgresql.conf)
Дата
Msg-id CA+OCxow2biL-bvgY+qB3zhK=vhHmWHLEeArRx6ZKQzA=8+6+Jg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Crash in pgadmin3 (Recent Files for postgresql.conf)  (Ashesh Vashi <ashesh.vashi@enterprisedb.com>)
Ответы Re: Crash in pgadmin3 (Recent Files for postgresql.conf)  (Ashesh Vashi <ashesh.vashi@enterprisedb.com>)
Список pgadmin-hackers
Thanks, patch applied.

On Mon, Oct 8, 2012 at 8:41 AM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:

On Sun, Oct 7, 2012 at 11:17 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
HI List,

We found a weird bug in pgAdmin3 (1.16) on Ubuntu and Windows 7.

Step to reproduce it:
1. File->Open postgresql.conf
2. Open any postgresql.conf on the file system. (This will open Backend Configuration Editor)
In Backend Configuration Editor:
3. File->Recent Files-><previous-selected-conf-file>
And, boom!!!

NOTE: Select any of the recently opened file and pgAdminIII will crash.

Here is the patch to resolve the issue.
Please find the updated patch, which resolves the issue much simpler way.

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: 
Enterprise PostgreSQL Company


http://www.linkedin.com/in/asheshvashi 


--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA:
Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi





--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers




--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

В списке pgadmin-hackers по дате отправления:

Предыдущее
От: Dave Page
Дата:
Сообщение: pgAdmin III commit: Prevent a crash when opening a second config file i
Следующее
От: Dave Page
Дата:
Сообщение: pgAdmin III commit: Don't autosize the search results columns if no res