From: | "Harald Armin Massa" <haraldarminmassa(at)gmail(dot)com> |
---|---|
To: | pgadmin-support(at)postgresql(dot)org |
Subject: | Crashes in Query Window - PgAdmin 1.6 Beta SVN Head |
Date: | 2006-09-20 09:58:52 |
Message-ID: | 7be3f35d0609200258t6c33e910yd47ee65f669568f3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hello,
I am using a kindly-by-Dave-provided PgAdmin 1.6 Beta from SVN Head as of
2006-09-19 9:07.
Within the Query Window I am developping a query:
select md5(id_rf::text||coalesce(wert,'x')||id_rk::text||id_bf), * from
repofeld <F5>
select
md5(id_rf::text||coalesce(wert,'x')||id_rk::text||id_bf||anothercol1), *
from repofeld <F5>
select
md5(id_rf::text||coalesce(wert,'x')||id_rk::text||id_bf||anothercol1||anothercol2),
* from repofeld <F5>
[....]
and after around 20-30 runs of this query, PgAdmin "hard crashes" (phone
home to MS type of crash)
As much as I am able to analyze, it happens after numerous queries
containing "no real colums" -> that md5(whatever) is ?column? in output, and
everytime a different result - as I am developing this function (learning
where I have to cast by hand etc...)
Can it be that the "caching of column heads" could be responsible in some
way, Dave?
If I can do anything more to make it reproducable, please let me know.
Harald
--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Reinsburgstraße 202b
70197 Stuttgart
0173/9409607
-
Let's set so double the killer delete select all.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2006-09-20 10:03:22 | Re: pgAgent Job never starts |
Previous Message | Dave Page | 2006-09-19 15:53:35 | Re: pgAgent Job never starts |