Roberto Icardi wrote:
Also, please set pgAdmin to 'Debug' log level (under File->Options),
create a new log of you recreating the crash (using direct debugging,
not a global breakpoint) and then send me the logfile.
Done
Doesn't shed any light though unfortunately. Do you have a firewall on
I've tried on the win2000 virtual machine (running on virtualpc 2007)...
same error!
So, or I make something wrong (but I really don't understand what), or is
that particular pc,
or maybe uninstalling 8.2 left something dirty for 8.3. I need a clean vm
for testing
third option, but requires some
Also, please set pgAdmin to 'Debug' log level (under File->Options),
create a new log of you recreating the crash (using direct debugging,
not a global breakpoint) and then send me the logfile.
Done
Doesn't shed any light though unfortunately. Do you have a firewall on
that box? If so, can yo
Roberto Icardi wrote:
>> When you attempt to debug it, do you see the parameter dialogue before
>> it crashes, or does it go immediately?
>>
>
> if I try debug->debug it goes immediately
> if I try debug->set breakpoint I can see debugger window but is
> completely empty and inactive
>
>
>
>> A
- Original Message -
From: "Roberto Icardi" <[EMAIL PROTECTED]>
To: "Dave Page" <[EMAIL PROTECTED]>
Sent: Monday, October 22, 2007 5:31 PM
Subject: Re: [HACKERS] pgadmin debug on windows
When you attempt to debug it, do you see the parameter dialogue
Roberto Icardi wrote:
> CREATE OR REPLACE FUNCTION public.prova(provain character varying)
> RETURNS character varying AS
> $BODY$
> begin
> if (provain = 'A') then
>return 'INVALIDO';
> else
>return 'VALIDO';
> end if;
> end;
> $BODY$
> LANGUAGE 'plpgsql' VOLATILE
> COST 100;
> ALTER
Please post the definition of an affected function, along with the
output from the following queries:
select * from pldbg_get_proxy_info();
select * from pldbg_get_target_info('16480', 'o');
(where 16480 is replaced with the oid of the affected function).
Thanks, Dave
CREATE OR REPLACE FUN
Roberto Icardi wrote:
> Yes, they are all there
> I've also tried on a newly created database instead of testing on a
> restored from 8.2. backup but with
> the same behaviour :-(
Please post the definition of an affected function, along with the
output from the following queries:
select * fr
ED]>
Cc:
Sent: Monday, October 22, 2007 4:09 PM
Subject: Re: [HACKERS] pgadmin debug on windows
Roberto Icardi wrote:
Dave,
the problem isn't with a particular function. Debug does not work with
every function I try, even with the simplest one, always with the same
behaviour I'v
Roberto Icardi wrote:
> Dave,
>
> the problem isn't with a particular function. Debug does not work with
> every function I try, even with the simplest one, always with the same
> behaviour I've previously explained.
> I repeat, my postgresql server is an 8.3 beta 1 installed on the same
> machin
Dave,
the problem isn't with a particular function. Debug does not work with every
function I try, even with the simplest one, always with the same behaviour I've
previously explained.
I repeat, my postgresql server is an 8.3 beta 1 installed on the same machine
where pgadmin III 1.8 is insta
Roberto Icardi wrote:
> Hello,
>
> I've installed on a windows xp machine beta 1 of postgresql 8.3 and
> pgadmin III 1.8.
> I've loaded a backup of a database from a 8.2.5 machine, for testing
> purpose, and tried
> the new functionality of plpgsql debug of functions.
>
> But I was disappointed
Hello,
I've installed on a windows xp machine beta 1 of postgresql 8.3 and pgadmin III
1.8.
I've loaded a backup of a database from a 8.2.5 machine, for testing purpose,
and tried
the new functionality of plpgsql debug of functions.
But I was disappointed to see that does not work.
I try to deb
13 matches
Mail list logo
