From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pgadmin-support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: PgAdmin III 1.12 crazy memory usage |
Date: | 2010-10-12 09:47:32 |
Message-ID: | AANLkTinGtw8Gd1ED_D1Y2h6QpWTbfaRZ75EPMfVX_t+8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On 12 October 2010 10:41, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On Thu, Oct 7, 2010 at 4:59 PM, Guillaume Lelarge
> <guillaume(at)lelarge(dot)info> wrote:
>> Le 07/10/2010 13:56, Dave Page a écrit :
>>> On Tue, Oct 5, 2010 at 11:03 AM, Thom Brown <thom(at)linux(dot)com> wrote:
>>>> Okay, I've tried reproducing it by asking it to show the edit view
>>>> without restricting the number of results, but seems to be fine. But
>>>> if I open with limited to 100, then change it to "no limit", refresh
>>>> and close, the query still appears to be running on the server. It
>>>> shows "pgAdmin III - Edit Grid" as the process running the query too,
>>>> and there's still lots of I/O on the machine. I definitely don't
>>>> still have that window open.
>>>
>>> OK, so I believe the attached patch fixes this, though I'm slightly
>>> nervous about unintended side-effects. I'll provide Thom with a binary
>>> for testing, but would appreciate it if someone else (Guillaume?)
>>> could also review the patch.
>>>
>>
>> Seems good to me. I don't find any side-effects on this patch. So +1 to
>> commit it.
>
> Done.
Thanks Dave.
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2010-10-12 10:08:00 | Re: Postgres Version |
Previous Message | Dave Page | 2010-10-12 09:41:38 | Re: PgAdmin III 1.12 crazy memory usage |