Oh, great - thanks for confirming and taking the initiative to do so. Can you minimise your app down to a simple test case (ideally a patch against one of the wxWidgets sample apps,as the wx guys prefer those), and log a bug on the wxWidgets Trac site?
Thanks. On Thu, Jul 18, 2013 at 3:23 PM, Dinesh Kumar <dinesh.ku...@enterprisedb.com > wrote: > Hi Dave/Dhiraj, > > Sorry for interfering here. > > Today i have tested the same case in my local windows machine and facing > the same problem. I have setup a sample grid environment using code blocks > IDE and with the data provided. I am able to reproduce the same case. Grid > is not able to place the many characters like (id=>1113, > length(content)=>1102145 and id=>1124, length(content)=>2319784). If i > select all the columns except these two id's then it's fine. If i select > all the rows including these two rows, then the cpu load is increasing very > high in my local windows machine. I believe it's the problem with wxWidgets > or wxGrid internal implementation. > > Thanks in advance. > > Dinesh > > -- > *Dinesh Kumar* > Software Engineer > > Ph: +918087463317 > Skype ID: dinesh.kumar432 > www.enterprisedb.co > <http://www.enterprisedb.com/>m<http://www.enterprisedb.com/> > * > Follow us on Twitter* > @EnterpriseDB > > Visit EnterpriseDB for tutorials, webinars, > whitepapers<http://www.enterprisedb.com/resources-community> and > more <http://www.enterprisedb.com/resources-community> > > > On Thu, Jul 18, 2013 at 7:17 PM, Dave Page <dp...@pgadmin.org> wrote: > >> On Wed, Jul 17, 2013 at 4:53 PM, Philip Luppens >> <philip.lupp...@gmail.com> wrote: >> > On Wed, Jul 17, 2013 at 5:41 PM, Dave Page <dp...@pgadmin.org> wrote: >> >> >> >> On Wed, Jul 17, 2013 at 4:36 PM, Philip Luppens >> >> <philip.lupp...@gmail.com> wrote: >> >> > >> >> > >> >> > >> >> > On Wed, Jul 17, 2013 at 5:28 PM, Dave Page <dp...@pgadmin.org> >> wrote: >> >> >> >> >> >> Hi >> >> >> >> >> >> On Wed, Jul 17, 2013 at 4:23 PM, Philip Luppens >> >> >> <philip.lupp...@gmail.com> wrote: >> >> >> > Good day everyone, >> >> >> > >> >> >> > I'd like to discuss an issue in the current stable version 1.16.1 >> of >> >> >> > pgAdmin3 that has been reported before [1], but since no solution >> was >> >> >> > reported, I'd like to ask for a bit of followup. >> >> >> > >> >> >> > The issue is pretty much as described in [1]: displaying rows with >> >> >> > type >> >> >> > TEXT >> >> >> > with some content (smallish XML documents) renders the application >> >> >> > unusable >> >> >> > for a long duration. The retrieval is plenty fast, only the >> rendering >> >> >> > in >> >> >> > pgAdmin3 is affected. Since I have no experience with C++ nor >> >> >> > wxWidgets, >> >> >> > I'm >> >> >> > afraid I cannot offer more than a simple profiling [2]. To the >> >> >> > untrained >> >> >> > eye, this seems like a problem in the wxWidgets library (correct >> me >> >> >> > if >> >> >> > I'm >> >> >> > wrong). >> >> >> > >> >> >> > I did some searching in the wxWidgets Traq instance, and all I >> found >> >> >> > was >> >> >> > this issue [3], but I'm not sure it's related - which was >> >> >> > acknowledged 5 >> >> >> > years ago. Does that mean there's no hope of this getting >> resolved? >> >> >> > Or >> >> >> > is it >> >> >> > such a minor issue for most people? >> >> >> > >> >> >> > In the mean time, I'm using a commercial offering, but I'd rather >> see >> >> >> > the >> >> >> > pgAdmin3 tool getting a fix for OSX developers. However, if this >> >> >> > boils >> >> >> > down >> >> >> > to 'not our fault - go and bug the wxWidgets guys', then I >> completely >> >> >> > understand that. >> >> >> > >> >> >> > Cheers, >> >> >> > >> >> >> > Phil >> >> >> > >> >> >> > >> >> >> > [1] >> >> >> > >> >> >> > >> >> >> > >> http://www.postgresql.org/message-id/caguhjrmgbcoanenekvxbbzni82n-1re9qd-gravv_b6r2gu...@mail.gmail.com >> >> >> > [2] http://i.imgur.com/DMEXeps.png >> >> >> > [3] http://trac.wxwidgets.org/ticket/4408 >> >> >> >> >> >> Can you provide a test case that is slow for you? I've never seen >> such >> >> >> a problem and use OSX daily. >> >> > >> >> > >> >> > Sure - how would one prepare such a test case? A simple DB dump with >> >> > data? >> >> >> >> Yes please. >> > >> > >> > Ok, I've uploaded an archive [1] - let me know if that works (there's >> quite >> > a few options in the backup routine, and I'm not sure which ones I'd >> need to >> > select, so give me a shout if I forgot something. >> > >> > It contains a single table content with the following structure: >> > >> > CREATE TABLE content ( >> > id bigint NOT NULL, >> > content text, >> > content_type character varying(10) NOT NULL, >> > documentid character varying(512) NOT NULL >> > ); >> > >> > >> > Any display of the records in the table via pgAdmin results immediately >> in a >> > complete lockdown of the application for +/- 30 seconds, and results in >> the >> > profiling that I've linked to in the OP. >> > >> >> Hi >> >> Thanks - I can reproduce this on a 16GB machine as well. It does look >> to me as if it's likely a wxWidgets issue - if I use pgAdmin 1.18 >> which has a working limit on the number of chars it'll attempt to >> display in the query tool, it's very fast (when set to 1024), but when >> opened in the Edit Grid, it takes a significant time to open the >> table. >> >> Dhiraj; can you see if you can do some profiling to confirm whether or >> not it is wxWidgets, or if we have a bug somewhere please? >> >> Thanks. >> >> -- >> 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 >> > > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
