Re: Crash on delete record with filter in place

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Colin Beckingham <colbec(at)start(dot)ca>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: Crash on delete record with filter in place
Date: 2011-09-20 19:53:48
Message-ID: 1316548428.2086.17.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

On Tue, 2011-09-20 at 10:48 -0400, Colin Beckingham wrote:
> On 09/19/2011 04:53 PM, Colin Beckingham wrote:
> >
> >
> > On 09/19/2011 03:12 PM, Guillaume Lelarge wrote:
> >> On Sat, 2011-09-17 at 17:45 -0400, Colin Beckingham wrote:
> >>> Using pgadmin 1.15 Dev on Opensuse 11.4, kernel 3.0.
> >>>
> >>> Viewing the data in a table with full data set visible, select a record
> >>> for delete, run delete, record is deleted correctly, pgadmin continues
> >>> to run.
> >>>
> >>> View the data in a table and place a filter to show subset of records.
> >>> Attempt to delete a row. This is permitted by the menus. Row is deleted
> >>> correctly, however pgadmin immediately crashes both the main and the
> >>> view data windows. Data is intact, restarting pgadmin allows to continue
> >>> as before.
> >>
> >> I don't manage to get a reproducible test case. I mean, I do get some
> >> crashes, but they are mostly random. Something that would crash pgAdmin
> >> once won't work twice. Which doesn't help fixing it.
> >>
> >>
> >
> > Well, so far 1.15 has been working well for me. This incident (which I
> > managed to repeat several times) was the only time it has let me down.
> >
> > I tried setting up a simple table to repeat the issue I reported but I
> > admit I failed to repeat it. On my small test table with oids in place I
> > was able to delete records with no filter in place or with a filter. It
> > worked fine.
> >
> > I am reluctant to attempt a repeat the crash with my other table which
> > is important right now - I will try to recreate the crash on a copy
> > later. This other table is much larger and more complex.
> >
> > In my investigation I did seem to find that tables with oids in place
> > allowed me to delete a record via the toolbar icon, but the right click
> > contextual submenu items remained greyed out. Table without oids on
> > select a record or set of records does not activate the delete records
> > icon on the toolbar or in the contextual submenu.
> >
> > An exception to the observation on context submenu in the last para. If
> > the data is entered through the insert script, and then you open the
> > view data - view all rows, the context menu does not work. However if
> > you enter data _into_ the view data table this then activates the
> > context menu and you can delete.
> >
> > More later.
>
> Oki doki, some more information for you.
>
> I have repeated the error, it is now crashing with no filter in place.
>

It does so with me too.

> Short feedback:
> gdb says:
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff70b34a7 in wxGridCellAttrData::UpdateAttrRows(unsigned long,
> int) ()
> from /usr/lib64/wx-2.8-wxcontainer/libwx_gtk2u_adv-2.8.so.0
>
> Long feedback:
> 1. using a table with 10,000+ records, with oids, with serial field, and
> about 5 other numeric and text fields. I can send you the entire copy
> version if you would like it
> 2. no external relations or indexes involved apart from the serial field
> 3. go into view data, select a record, toolbar icon lights up
> 4. click toolbar icon, record disappears and pgadmin goes with it.
>

Well, I don't think we need the whole definition. It already crashes
with a one-column table.

But thanks for the info :)

--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Willy-Bas Loos 2011-09-21 10:24:11 Re: pgadmin3 crash report
Previous Message Guillaume Lelarge 2011-09-20 19:52:26 Re: Crash on delete record with filter in place