Re: [pgadmin-hackers] [pgadmin-support] FW: oids bug
Michael Shapiro wrote: I forgot to send you the trigger for this table. It turns out that the trigger raises an exception when an update on the packet_id occurs. At 07:34 PM 11/26/2003 +0100, you wrote: Michael Shapiro wrote: NOTE, I am running Windows XP, PgAdmin 1.1.0 Devel(Nov 21 2003) win32 version shouldn't make any difference. There has been a similar observation some days ago, which disappeared after recreation of the table (which sounds like magic to me). I'd be glad if we could find the problem; pgAdmin3 may not crash whatever data should be in the backend. Finally, I found it. After executing a query in a thread, the pointer to the notice processing routine was dangling. An update wouldn't execute in a thread, but directly, receiving a NOTICE into the wild. New version committed to cvs, win32 binary upload to follow. This might fix the Edit Data problem previously reported by Jonathan Mezach too. Regards, Andreas ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] Error message while connecting to a UNICODE
Andreas Pflug wrote: Raphaël Enrici wrote: ... And here is pgadmin3 log file: 2003-11-26 19:25:37 INFO : Destroying a connect dialogue 2003-11-26 19:25:37 STATUS : Connecting to database... 2003-11-26 19:25:37 INFO : Creating pgConn object 2003-11-26 19:25:37 INFO : Server name: 192.169.0.254 (resolved to: 192.169.0.254) 2003-11-26 19:25:37 INFO : Opening connection with connection string: hostaddr='192.169.0.254' dbname='template1' user='xxx' password='yyy' port=5432 2003-11-26 19:25:37 QUERY : Set query (192.169.0.254:5432): SELECT pg_encoding_to_char(encoding) AS encoding, datlastsysoid FROM pg_database WHERE datname='template1' 2003-11-26 19:25:37 INFO : Creating pgSet object 2003-11-26 19:25:37 INFO : Setting client_encoding to 'UNICODE' 2003-11-26 19:25:37 ERROR : ?T (the final '?' are not mine... they are in the logfile). If it's a known issue, just tell me to go to bed (I promise, I'll do it)! Sorry, you must stay awake :-P hehe, what will my wife say! :-p Does the user name contain non-ASCII chars? not at all. The user I use is "ralph"... ooops I said it :) Regards, Raphaël ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [pgadmin-hackers] Error message while connecting to a UNICODE
Raphaël Enrici wrote: Dear friends, while testing things for hiroshi, I found this problem on my installation: (I read the FAQ and BUGS.txt, but as you know I'm not a good reader and I always need to wash my eyes... :p) pgsql server 7.3.4 with db created in "UNICODE". pgadmin3 latest snapshot (today's one) Observed on debian stable and unstable When I connect to the db, I have a popup window telling me that "An Error occured". On the console I can see this warning: ** (pgadmin3:24606): WARNING **: Invalid UTF8 string passed to pango_layout_set_text() And here is pgadmin3 log file: 2003-11-26 19:25:37 INFO : Destroying a connect dialogue 2003-11-26 19:25:37 STATUS : Connecting to database... 2003-11-26 19:25:37 INFO : Creating pgConn object 2003-11-26 19:25:37 INFO : Server name: 192.169.0.254 (resolved to: 192.169.0.254) 2003-11-26 19:25:37 INFO : Opening connection with connection string: hostaddr='192.169.0.254' dbname='template1' user='xxx' password='yyy' port=5432 2003-11-26 19:25:37 QUERY : Set query (192.169.0.254:5432): SELECT pg_encoding_to_char(encoding) AS encoding, datlastsysoid FROM pg_database WHERE datname='template1' 2003-11-26 19:25:37 INFO : Creating pgSet object 2003-11-26 19:25:37 INFO : Setting client_encoding to 'UNICODE' 2003-11-26 19:25:37 ERROR : ?T (the final '?' are not mine... they are in the logfile). If it's a known issue, just tell me to go to bed (I promise, I'll do it)! Sorry, you must stay awake :-P Does the user name contain non-ASCII chars? Regards, Andreas ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[pgadmin-hackers] Error message while connecting to a UNICODE db
Dear friends, while testing things for hiroshi, I found this problem on my installation: (I read the FAQ and BUGS.txt, but as you know I'm not a good reader and I always need to wash my eyes... :p) pgsql server 7.3.4 with db created in "UNICODE". pgadmin3 latest snapshot (today's one) Observed on debian stable and unstable When I connect to the db, I have a popup window telling me that "An Error occured". On the console I can see this warning: ** (pgadmin3:24606): WARNING **: Invalid UTF8 string passed to pango_layout_set_text() And here is pgadmin3 log file: 2003-11-26 19:25:37 INFO : Destroying a connect dialogue 2003-11-26 19:25:37 STATUS : Connecting to database... 2003-11-26 19:25:37 INFO : Creating pgConn object 2003-11-26 19:25:37 INFO : Server name: 192.169.0.254 (resolved to: 192.169.0.254) 2003-11-26 19:25:37 INFO : Opening connection with connection string: hostaddr='192.169.0.254' dbname='template1' user='xxx' password='yyy' port=5432 2003-11-26 19:25:37 QUERY : Set query (192.169.0.254:5432): SELECT pg_encoding_to_char(encoding) AS encoding, datlastsysoid FROM pg_database WHERE datname='template1' 2003-11-26 19:25:37 INFO : Creating pgSet object 2003-11-26 19:25:37 INFO : Setting client_encoding to 'UNICODE' 2003-11-26 19:25:37 ERROR : ?T (the final '?' are not mine... they are in the logfile). If it's a known issue, just tell me to go to bed (I promise, I'll do it)! Any idea ? Regards, Raphaël ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] Windows-XP and 2003 Problem's patch to wxWindows
Hi Andreas. It is completely good. Hopefully.:-) I am a little sleepy... regards, Hiroshi Saito From: "Andreas Pflug" <[EMAIL PROTECTED]> > Hiroshi Saito wrote: > > >First of all I showed the need of the modification. > >https://sourceforge.net/tracker/index.php?func=detail&aid=849433&group_id=9863&atid=309863 > >It is thought to make the most of it as a material to proceed in a solution of a > >problem. > > > > > > Nice catch! > > For our purposes, we could apply that patch, or simply comment out all > WM_ERASEBACKGND handling in wxNotebook::MSWWindowProc (reducing it to > forwarding all events to wxControl::MSWWindowProc). Final wx solution > will probably look different, but we don't need to care. > > My next binary snapshot upload will include this solution, fixing. > > Regards, > Andreas ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[pgadmin-hackers] [querybuilder patch] Re: I asks for again, And Apology.
Hi Hiroshi, Hiroshi Saito wrote: Question 1) Can you operate QueryBuilder well? Here are the quick tests I did : I tried to launch the querybuilder from today's snapshots (debian stable version) and it simply crashes when I select a table to add... I then took your patch and applied it. Now I can select the table to add but I have some wx asserts: src/common/list.cpp(326): assert "wxAssertFailure" failed: invalid index in wxListBase::Item Do you want to stop the program? You can also choose [Cancel] to suppress further warnings. [I click NO] src/generic/listctrl.cpp(1304): assert "wxAssertFailure" failed: invalid column index in SetItem Do you want to stop the program? You can also choose [Cancel] to suppress further warnings. [I click NO] src/common/list.cpp(326): assert "wxAssertFailure" failed: invalid index in wxListBase::Item Do you want to stop the program? You can also choose [Cancel] to suppress further warnings. [I click NO] It's ok. These asserts are coming up everytime I add a table and in the same order. Question 2) Please send screen shots to me. Shall I ? Question 3) What is Version of gcc and gtk? gcc 2.95.4-11woody1 libgtk2: 2.2.2-1woody2 If you want I can try a build on debian unstable ( it should be libgtk2=2.2.4-1 and gcc 3.3.2-1) Hope this helps, Raphaël Enrici ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] Windows-XP and 2003 Problem's patch to wxWindows
Hiroshi Saito wrote: First of all I showed the need of the modification. https://sourceforge.net/tracker/index.php?func=detail&aid=849433&group_id=9863&atid=309863 It is thought to make the most of it as a material to proceed in a solution of a problem. Nice catch! For our purposes, we could apply that patch, or simply comment out all WM_ERASEBACKGND handling in wxNotebook::MSWWindowProc (reducing it to forwarding all events to wxControl::MSWWindowProc). Final wx solution will probably look different, but we don't need to care. My next binary snapshot upload will include this solution, fixing. Regards, Andreas ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[pgadmin-hackers] Windows-XP and 2003 Problem's patch to wxWindows
Hi Dave. When I examine it so far, Problem is shown remarkably with Windows-XP and 2003. Former patch was the thing to indicate the problem place clearly. Then, a problem is complex though it could be cleared to a certain extent. First of all I showed the need of the modification. https://sourceforge.net/tracker/index.php?func=detail&aid=849433&group_id=9863&atid=309863 It is thought to make the most of it as a material to proceed in a solution of a problem. However, Application to our wxWindows worries whether I should wait for the result. any idea? When patch is applied, a solution is done. http://cre-ent.skcapi.co.jp/~saito/pgadmin3/comctl32_patch_After.jpg regards, Hiroshi Saito notebook_ComCtl_patch Description: Binary data ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] [pgadmin-support] SSL connections and Query
Jean-Michel POURE wrote: Le Mardi 25 Novembre 2003 22:14, Andreas Pflug a écrit : Can somebody please find out what's the difference between today's FC1 snapshot and previous crashing ones? Hopefully, we can nail this problem down to some compile/linker option. We didn't have any code change in this section for quite a while. Dear Andreas, Fantastic, we are getting close to explaining the prolem. To my knowledge, there is no difference in the RPM spec. Devrim, do you have any idea? IMHO, it should be a problem with shared libraries. Timothy, did you happen to upgrade some RPMs from Fedora when installing pgAdmin3 RC1 snapshot? Is it a difference in wxWindows versions, perhaps? ahp ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] pgAdmin3 solaris
Andreas Pflug wrote: Raphaël Enrici wrote: I'm currently still trying a build on solaris 8 (consider this as an announce to become solaris porter for pgA3 if nobody else wants to do it ;p) Nice too! :) > but with no luck... What's the problem on Solaris? Hi Andreas, For the moment I get errors while building our wx snapshot on it. I didn't get the time to try a build of an official one. I can't publish build logs at all for the moment. As far as I've read, wx should build correctly on solaris and the errors I get seem to be linked to sparc 64 arch not well detected... I'll do more report asap. Regards, Raphaël ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] pgObject_statistic_patch
Thanks Hiroshi, patch applied. Regards, Dave. > -Original Message- > From: Hiroshi Saito [mailto:[EMAIL PROTECTED] > Sent: 26 November 2003 06:12 > To: Dave Page > Cc: [EMAIL PROTECTED] > Subject: pgObject_statistic_patch > > Hi Dave. > > The icon of the unnecessary statistics information exists. > Please apply it. > > regards, > Hiroshi Saito > ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] [pgadmin-support] SSL connections and Query tool
Le Mardi 25 Novembre 2003 22:14, Andreas Pflug a écrit : > Can somebody please find out what's the difference between today's FC1 > snapshot and previous crashing ones? Hopefully, we can nail this problem > down to some compile/linker option. We didn't have any code change in > this section for quite a while. Dear Andreas, Fantastic, we are getting close to explaining the prolem. To my knowledge, there is no difference in the RPM spec. Devrim, do you have any idea? IMHO, it should be a problem with shared libraries. Timothy, did you happen to upgrade some RPMs from Fedora when installing pgAdmin3 RC1 snapshot? Cheers, Jean-Michel Pouré ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
