Thread: PgAdmin3 1.4.1 on Mac OSX 1.4.1 is unusable....

PgAdmin3 1.4.1 on Mac OSX 1.4.1 is unusable....

From
Jerry LeVan
Date:
I guess the subject says it all. I replaced 1.4.0 with
1.4.1 and many, many commands kill the application.
(even select * from foo limit 100).

I am running the latest MacOS X 10.4.3 and Postgresql 8.1.1.

Where can I find 1.4.0, it seemed to be reasonably stable!

Jerry


Re: PgAdmin3 1.4.1 on Mac OSX 1.4.1 is

From
Dave Page
Date:


On 14/12/05 7:05 pm, "Jerry LeVan" <jerry.levan@eku.edu> wrote:

> I guess the subject says it all. I replaced 1.4.0 with
> 1.4.1 and many, many commands kill the application.
> (even select * from foo limit 100).

Eeep, that's not good :-(. I'm investigating now (thanks for the report)
> I am running the latest MacOS X 10.4.3 and Postgresql 8.1.1.
> 
> Where can I find 1.4.0, it seemed to be reasonably stable!

http://www.postgresql.org/ftp/pgadmin3/release/v1.4.0/osx


Regards, Dave 




Re: PgAdmin3 1.4.1 on Mac OSX 1.4.1 is

From
Dave Page
Date:


On 14/12/05 9:12 pm, "Dave Page" <dpage@vale-housing.co.uk> wrote:

> 
> 
> 
> On 14/12/05 7:05 pm, "Jerry LeVan" <jerry.levan@eku.edu> wrote:
> 
>> I guess the subject says it all. I replaced 1.4.0 with
>> 1.4.1 and many, many commands kill the application.
>> (even select * from foo limit 100).
> 
> Eeep, that's not good :-(. I'm investigating now (thanks for the report)
>  

Now this is strange - I can reproduce this in 1.4.1 with any query in the
query tool, including SELECT 1; or SELECT * fROM pg_class; However, SVN
trunk, and 1.4.0 work just fine (I've done complete rebuilds of trunk and
1.4.1 on the same box. Didn't bother with 1.4.0).

It bails out with the following at the tip of the back trace:

#0  0x00008c40 in pgConnBase::RegisterNoticeProcessor(void (*)(void*, char
const*), void*) ()
#1  0x0000ab08 in pgQueryThreadBase::pgQueryThreadBase(pgConnBase*, wxString
const&, int) ()
#2  0x00014a04 in pgQueryThread::pgQueryThread(pgConnBase*, wxString const&,
int) ()
#3  0x000bb714 in ctlSQLResult::Execute(wxString const&, int) ()
#4  0x000e20bc in frmQuery::execQuery(wxString const&, int, bool, int, bool)
()
#5  0x000e1b44 in frmQuery::OnExecute(wxCommandEvent&) ()

Now I can't see any changes at all that should affect
RegisterNoticeProcessor - which is even wierder when you consider that all
the changes to 1.4.x are also present in trunk. On a hunch I rolled back to
PostgreSQL 8.1.0, but that didn't make any difference.

Anyone got any ideas? Florian, could you try a build of 1.4.1 and trunk, and
if so, do they work for you?

Regards, Dave 




Re: PgAdmin3 1.4.1 on Mac OSX 1.4.1 is

From
Andreas Pflug
Date:
Dave Page wrote:
> 
> 
> On 14/12/05 9:12 pm, "Dave Page" <dpage@vale-housing.co.uk> wrote:
> 
> 
>>
>>
>>On 14/12/05 7:05 pm, "Jerry LeVan" <jerry.levan@eku.edu> wrote:
>>
>>
>>>I guess the subject says it all. I replaced 1.4.0 with
>>>1.4.1 and many, many commands kill the application.
>>>(even select * from foo limit 100).
>>
>>Eeep, that's not good :-(. I'm investigating now (thanks for the report)
>> 
> 
> 
> Now this is strange - I can reproduce this in 1.4.1 with any query in the
> query tool, including SELECT 1; or SELECT * fROM pg_class; However, SVN
> trunk, and 1.4.0 work just fine (I've done complete rebuilds of trunk and
> 1.4.1 on the same box. Didn't bother with 1.4.0).
> 
> It bails out with the following at the tip of the back trace:
> 
> #0  0x00008c40 in pgConnBase::RegisterNoticeProcessor(void (*)(void*, char
> const*), void*) ()
> #1  0x0000ab08 in pgQueryThreadBase::pgQueryThreadBase(pgConnBase*, wxString
> const&, int) ()
> #2  0x00014a04 in pgQueryThread::pgQueryThread(pgConnBase*, wxString const&,
> int) ()
> #3  0x000bb714 in ctlSQLResult::Execute(wxString const&, int) ()
> #4  0x000e20bc in frmQuery::execQuery(wxString const&, int, bool, int, bool)
> ()
> #5  0x000e1b44 in frmQuery::OnExecute(wxCommandEvent&) ()
> 
> Now I can't see any changes at all that should affect
> RegisterNoticeProcessor - which is even wierder when you consider that all
> the changes to 1.4.x are also present in trunk. On a hunch I rolled back to
> PostgreSQL 8.1.0, but that didn't make any difference.
> 
> Anyone got any ideas? Florian, could you try a build of 1.4.1 and trunk, and
> if so, do they work for you?

Try using the previous ctlComboBox.h version. GetSelection is a virtual 
method, maybe it's some compiler problem. I noticed the last wxComboBox 
problem just in frmQuery, maybe the connections stored in the combobox 
are screwed up.

Regards,
Andresa


Re: PgAdmin3 1.4.1 on Mac OSX 1.4.1 is unusable....

From
"Dave Page"
Date:

> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Jerry LeVan
> Sent: 14 December 2005 19:06
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] PgAdmin3 1.4.1 on Mac OSX 1.4.1 is
> unusable....
>
> I guess the subject says it all. I replaced 1.4.0 with
> 1.4.1 and many, many commands kill the application.
> (even select * from foo limit 100).
>
> I am running the latest MacOS X 10.4.3 and Postgresql 8.1.1.

Hi Jerry

I think I've got this sorted now - it seems that the wx API changes we
found in wx 2.6.2 weren't completely resolved in the Mac port of pgAdmin
1.4.1. A build based on the latest 1.4 STABLE branch code (rev 4847) is
available at http://developer.pgadmin.org/~dpage/.

If you and Florian can confirm that this looks OK I'd appreciate it.
I'll then release it with a note to explain that it's actually
1.4.1.00001.

Regards, Dave.


Re: PgAdmin3 1.4.1 on Mac OSX 1.4.1 is unusable....

From
"Dave Page"
Date:

> -----Original Message-----
> From: Jerry LeVan [mailto:jerry.levan@eku.edu]
> Sent: 15 December 2005 16:59
> To: Dave Page
> Subject: Re: [pgadmin-support] PgAdmin3 1.4.1 on Mac OSX
> 1.4.1 is unusable....
>
>
> Well not quite settled out...
>
> Selects seem to work but I found that if I drill down in the
> left panel to where the tables in a db are shown and double
> click in the panel  a couple of times quickly that the app dies...

Hmm, I'm completely unable to reproduce that, however I am running
Panther not Tiger which might be a factor.

Can anyone else test on Tiger?

Regards, Dave


Re: PgAdmin3 1.4.1 on Mac OSX 1.4.1 is unusable....

From
"Dave Page"
Date:

> -----Original Message-----
> From: Jerry LeVan [mailto:jerry.levan@eku.edu]
> Sent: 16 December 2005 15:22
> To: Dave Page
> Subject: Re: [pgadmin-support] PgAdmin3 1.4.1 on Mac OSX
> 1.4.1 is unusable....
>
>
> Dave,
>
> In 1.4.0 if I drill down to the table name level in the left panel
> and double click on a
> table name a window named "Table Checks" pops up.
>
> In 1.4.1 the same action crashes the application.

Ahh, yes, I see. That's almost certainly more of the same problem caused
by the changes to the wxWidgets API. :-(

> Does the 1.4.1 I just received an announcement for clear this
> problem ?

No, that's the announcement from earlier in the week being approved.

Thanks for the clarification.

Regards, Dave


Re: PgAdmin3 1.4.1 on Mac OSX 1.4.1 is

From
"Florian G. Pflug"
Date:
Dave Page wrote:
> On 14/12/05 9:12 pm, "Dave Page" <dpage@vale-housing.co.uk> wrote:
>>On 14/12/05 7:05 pm, "Jerry LeVan" <jerry.levan@eku.edu> wrote:
>>>I guess the subject says it all. I replaced 1.4.0 with
>>>1.4.1 and many, many commands kill the application.
>>>(even select * from foo limit 100).
>>
>>Eeep, that's not good :-(. I'm investigating now (thanks for the report)
> Now this is strange - I can reproduce this in 1.4.1 with any query in the
> query tool, including SELECT 1; or SELECT * fROM pg_class; However, SVN
> trunk, and 1.4.0 work just fine (I've done complete rebuilds of trunk and
> 1.4.1 on the same box. Didn't bother with 1.4.0).
> 
> It bails out with the following at the tip of the back trace:
> 
> #0  0x00008c40 in pgConnBase::RegisterNoticeProcessor(void (*)(void*, char
> const*), void*) ()
> #1  0x0000ab08 in pgQueryThreadBase::pgQueryThreadBase(pgConnBase*, wxString
> const&, int) ()
> #2  0x00014a04 in pgQueryThread::pgQueryThread(pgConnBase*, wxString const&,
> int) ()
> #3  0x000bb714 in ctlSQLResult::Execute(wxString const&, int) ()
> #4  0x000e20bc in frmQuery::execQuery(wxString const&, int, bool, int, bool)
> ()
> #5  0x000e1b44 in frmQuery::OnExecute(wxCommandEvent&) ()
> 
> Now I can't see any changes at all that should affect
> RegisterNoticeProcessor - which is even wierder when you consider that all
> the changes to 1.4.x are also present in trunk. On a hunch I rolled back to
> PostgreSQL 8.1.0, but that didn't make any difference.
> 
> Anyone got any ideas? Florian, could you try a build of 1.4.1 and trunk, and
> if so, do they work for you?
I tried my nighty-build of the 1.4 branch
(http://developer.pgadmin.org/snapshots/osx/pgadmin3-1.4-20051214.tar.bz2),
and it seems to work fine. At least I was able to start pgAdmin3, 
connect to a db, open a sql window, and issue a few simple queries 
(Inserts and Selects). Non of the selects returned a lot of rows, though.

I'm building against wxMac 2.6.2 and postgresql 8.1.0
I'm bulding on panther, using gcc version
"3.3 20030304 (Apple Computer, Inc. build 1671)".

greetings, Florian Pflug