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. HTH, Phil > > > Note: I forgot some more env. details (not sure if they are relevant): > > - OSX 10.8.4 > > - MBP i7, 8GB ram, 240GB SSD > > > > -Phil > > > >> > >> > >> -- > >> Dave Page > >> Blog: http://pgsnake.blogspot.com > >> Twitter: @pgsnake > >> > >> EnterpriseDB UK: http://www.enterprisedb.com > >> The Enterprise PostgreSQL Company > > > > > > > > > > -- > > "We cannot change the cards we are dealt, just how we play the hand." - > > Randy Pausch > > > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > [1] https://dl.dropboxusercontent.com/u/467190/nsesa_content.zip -- "We cannot change the cards we are dealt, just how we play the hand." - Randy Pausch
