Prev: rolcanlogin vs. the flat password file
Next: xlogdump
From: Dave Page on 22 Oct 2007 10:30
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 * 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

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

From: "Roberto Icardi" on 22 Oct 2007 10:42

> 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 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 FUNCTION prova(character varying) OWNER TO postgres;

select * from pldbg_get_proxy_info();

"PostgreSQL 8.3devel on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2
(mingw-special)";80300;3;3924

select * from pldbg_get_target_info('18891', 'o');

18891;2200;1;"1043";"prova";"";"{provain}";16386;"public.prova";f;1043

Thank you for your interest


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

From: Dave Page on 22 Oct 2007 11:14
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 FUNCTION prova(character varying) OWNER TO postgres;
>
> select * from pldbg_get_proxy_info();
>
> "PostgreSQL 8.3devel on i686-pc-mingw32, compiled by GCC gcc.exe (GCC)
> 3.4.2 (mingw-special)";80300;3;3924
>
> select * from pldbg_get_target_info('18891', 'o');
>
> 18891;2200;1;"1043";"prova";"";"{provain}";16386;"public.prova";f;1043

OK, that looks as I'd expect (and debugs just fine for me!).

When you attempt to debug it, do you see the parameter dialogue before
it crashes, or does it go immediately?

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.

Thanks, Dave.

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(a)postgresql.org so that your
message can get through to the mailing list cleanly

From: Dave Page on 22 Oct 2007 15:24
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
>
>
>
>> 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 you try disabling it temporarily?

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

From: "Roberto Icardi" on 24 Oct 2007 16:12
>>> 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 you try disabling it temporarily?
>
> Regards, Dave.
>

Only the windows firewall, if you can call it a firewall <g>
Anyway, I've disabled, but without luck.
Only thing I can add is that on that pc there where a previous release of
PostgreSQL (8.2), uninstalled before 8.3 beta installation.
Now I'll try with a Win2000 virtual machine. On this machine is installed
8.2 also, that I'm uninstalling right now.

Regards


---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: rolcanlogin vs. the flat password file
Next: xlogdump