I keep trying to debug the SELECT test_debug('TEST', 1224312); function. Sometimes debugging works on version 1.0.3, and sometimes it doesn't. There is a normal execution of the function with the return of the result and there is no switch to debug mode. I also noticed that after the debugging process, if you simply execute the SELECT test_debug('TEST', 1224312); then its execution time is delayed by tens of seconds.

Also, after some attempts on the server side, there is a process that can only be killed.

The legacy PostgreSQL debugger has some limitations as it only outputs a subset of variable. It only outputs basic variables and arrays. Rows, records and structured type are discarded.

Compile the modified debugger is not technically difficult but requires a Linux platform as it's too complicated on Windows.

We can provide a Docker image of the PostgreSQL with the enhanced debugger:

• Based on legacy image
• Compile the enhanced debugger against modified sources
• Install and configure it in shared libraries

Describe the bug When I try to debug a function by right clicking and selecting "Debug Routine" in the explorer I receive the following error:

To Reproduce Steps to reproduce the behavior:

1. Create a schema and function to debug:

create schema if not exists test_schema;

create or replace function test_schema.debug_test() returns text as $$
begin
  return 'Test';
end;
$$ language plpgsql;

3. Richt click 'debug_test' in database explorer
4. Select 'Debug Routine'

Expected behavior Function is debugged

Desktop (please complete the following information):

• OS: Debian Linux Kernel 5.17.0-1-amd64
• DataGrip 2022.1.1
• PostgreSQL Debugger 221.1.2

Additional context Debugging the following from a console window works as expected:

select test_schema.debug_test();

Good afternoon, Sir. I am using your plugin_debugger (https://github.com/ng-galien/pldebugger) library built according to your instructions. I noticed that if in the declared variables there is a variable with the RECORD type, the debugging process ends with an error. [55000] ERROR: record "v_record" is not assigned yet The tuple structure of a not-yet-assigned record is indeterminate. It's easy to check. In your function, which goes for an example, added in the declaration v_record RECORD; and before RETURN pasted the code FOR v_record IN SELECT * FROM public.debug LOOP RAISE NOTICE '%', v_record.id; END LOOP;

CREATE FUNCTION test_debug(p_text text, p_int integer DEFAULT 0) RETURNS text LANGUAGE plpgsql AS $$ DECLARE v_int_array INT[] = ARRAY [6, 7, 8]; v_custom public.custom_type = (434, 'Custom')::public.custom_type; v_debug_array debug[]; v_debug debug; v_text TEXT = ''; v_int INT = 0; v_date DATE = NULL; v_record RECORD; BEGIN v_text = p_text; v_int_array = ARRAY_APPEND(v_int_array, p_int); SELECT * FROM public.debug LIMIT 1 INTO v_debug; v_int_array = ARRAY_APPEND(v_int_array, 3); SELECT ARRAY_AGG(d) FROM public.debug d INTO v_debug_array; v_int_array = ARRAY_APPEND(v_int_array, 5); v_int_array = ARRAY_APPEND(v_int_array, 7); v_text = 'TEST'; v_int = v_int + 1; v_date = CURRENT_DATE; SELECT ARRAY_AGG(id) FROM public.debug INTO v_int_array; FOR v_record IN SELECT * FROM public.debug LOOP RAISE NOTICE '%', v_record.id; END LOOP;

RETURN 'DEBUG END';

END $$;

JSON and JSONB variables outputs are just inlined and not exploded in the variable view.

For RECORD type, as it's returned as a ROW without type we can outputs it as JSONB.

@cvas71 what's your feelings about it?

Started a debugging session from the Database Explorer.

This worked once. The next time I invoked the same function, it just ran, no debugger.

M1 Mac, Postgres 14, IntelliJ

Describe the bug I see Routine not found error.

To Reproduce Steps to reproduce the behavior:

create schema s_test;

create or replace function s_test.test_debug(p_text text, p_int integer DEFAULT 0) returns text
  language plpgsql
as
$$
BEGIN
  return 'DEBUG END';
end
$$;

SELECT s_test.test_debug('TEST', 0);

Try debug last row.

Expected behavior Should debug routines in schemas

Screenshots

If in a function, add a comment before DECLARE or, for example, a special command such as #variable_conflict use_variable. When debugging, the cursor is set to a line lower than it should be.

Describe the bug Debugger execute function without stopping on it.

To Reproduce

create schema if not exists test_schema;

create or replace function test_schema.debug_test() returns text as $$
begin
  return 'A';
end;
$$ language plpgsql;

select test_schema.debug_test(); -- Try debug this

In Debug/Console window it show single line:

[NOTICE] PLDBGBREAK:27

In Service windows it show execution result:

Expected behavior Should stop on function body.

Additional context PostgreSQL 14.1 (Docker-edition) Plsql Debugger 1.1.0

Describe the bug Can't debug stored procedures.

To Reproduce Steps to reproduce the behavior:

create or replace procedure debug_proc_test() as $$
begin
  null;
end;
$$ language plpgsql;

-- Select here and click "Debug" button:
call debug_proc_test();

Expected behavior Should debug procedures (not functions only),

Screenshots

Overview

Identify the target procedure

Features

• [x] Document calling convention
• [x] Parse the call
• [x] Handle procedure schema
• [x] Handle argument schema
• [x] Test the best candidate
• [x] Handle quotes
• [x] Create procedure for detection support
• [x] Provide two modes for detection, with internal API and Fail back with Queries

Debugging an anonymous plpg function can be a great feature.

• [ ] Detect we are in an anonymous function in the editor
• [ ] Create a temporary function with the anonymous code in the target
• [ ] Debug it in direct mode
• [ ] Delete the temporary function at the end of debugging