Re: pgadmin crash on refresh

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: pgadmin crash on refresh
Дата
Msg-id AANLkTi=qmNUBtQidkbveR8dUiYx3Y-hJ=uysNCjQmJHH@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pgadmin crash on refresh  (Dave Page <dpage@pgadmin.org>)
Ответы Re: pgadmin crash on refresh  (Guillaume Lelarge <guillaume@lelarge.info>)
Список pgadmin-hackers
On Fri, Jan 21, 2011 at 13:35, Dave Page <dpage@pgadmin.org> wrote:
> On Fri, Jan 21, 2011 at 12:20 PM, Magnus Hagander <magnus@hagander.net> wrote:
>> On Wed, Jan 19, 2011 at 14:55, Dave Page <dpage@pgadmin.org> wrote:
>>> On Wed, Jan 19, 2011 at 12:18 PM, Magnus Hagander <magnus@hagander.net> wrote:
>>>> Opened database->catalogs->pg_catalogs->tables. Right click + refresh = crash.
>>>>
>>>> Don't have time to dig in right now myself, but here's a backtrace if
>>>> somebody wants to get started, or perhaps has a clue what it could
>>>> be...
>>>>
>>>> this is with  current git master tip, debugging enabled.
>>>
>>> Hmm, can't reproduce it on Windows. It does look an awful lot like
>>
>> Oh, additional point: you need to actually *expand* the tables node,
>> or it doesn't crash. Did you by any chance not do that?
>
> I did do that.
>
>>> this though: http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commit;h=9ec6b29fe3fbd9cc196d5e91b55f3697f02bcad8
>>
>> Nope. I reverted that patch (well, due to the style patch i couldn't,
>> but i commented out that one line it seems to add) and it still
>> crashes for me.
>
> There's little chance that that patch would cause (or fix) the problem
> you see - but a similar patch in a different place might be the fix.
>

I've created ticket 299 for this for now, so we don't loose track of it.


--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

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

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: pgAdmin III commit: Add a guru hint explaining why VACUUM FULL is bad
Следующее
От: "pgAdmin Trac"
Дата:
Сообщение: [pgAdmin III] #299: Crash on table refresh