From: | "Diego A(dot) Gil" <diego(at)adminsa(dot)com> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | Ivan Nejgebauer <ian-pgasup(at)uns(dot)ns(dot)ac(dot)yu>, Pgadmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Crash when editing object properties |
Date: | 2004-09-14 16:28:29 |
Message-ID: | 1095179309.3400.1.camel@roadwarrior.adminsa.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
I can reproduce bug in Fedora Core 2, post-beta cvs sources, 12 sep
2004.
Diego.
El mar, 14-09-2004 a las 10:33, Dave Page escribió:
>
> > -----Original Message-----
> > From: pgadmin-support-owner(at)postgresql(dot)org
> > [mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of
> > Ivan Nejgebauer
> > Sent: 14 September 2004 14:17
> > To: pgadmin-support(at)postgresql(dot)org
> > Subject: [pgadmin-support] Crash when editing object properties
> >
> > This should be reproducible:
> >
> > 1. Connect to the database of your choice.
> >
> > 2. Navigate to the "Tables" node in the tree view and select
> > it. The list of tables appears in the upper right pane.
> >
> > 3. Select a table in the upper right pane.
> >
> > 4. Click the "Display/Edit Properties" button in the toolbar. *BOOM*
> >
> > This also happens with table columns, functions and trigger
> > functions, but interestingly, not always with sequences.
>
> Nope, can't reproduce that here. What platform, server version etc. are
> you running?
>
> Regards, Dave
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2004-09-14 17:54:05 | Re: Crash when editing object properties |
Previous Message | Dave Page | 2004-09-14 13:33:51 | Re: Crash when editing object properties |