Is pgAdmin the only front-end to PostgreSQL debugger ? And is "a working pl/pgsql debugger" something core should care to maintain ?

From: Hannu Krosing <hannuk(at)google(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: Steve Senior <stevesenior(at)google(dot)com>
Subject: Is pgAdmin the only front-end to PostgreSQL debugger ? And is "a working pl/pgsql debugger" something core should care to maintain ?
Date: 2025-02-13 17:00:02
Message-ID: CAMT0RQQ19QZ9VfeepC5spbLWj5OOY-7u0aPVgWFWGcMUkr5+8A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hallo PostgreSQL Hackers,

We recently discovered an error where pgAdmin fails when stepping into
nested function calls (
https://github.com/pgadmin-org/pgadmin4/issues/8443 ).

So while waiting for this to be fixed I would want to know if there
are other debugger front-ends that could be used to do basic debugging
of pl/pgsql code ?

And would these need a separate debugging extension, or is "debugging"
meant to be a generic PostgreSQL server feature that has a
well-defined API ?

I know there used to be another debugger as part of OmniDB which had
its own server-side extension as well, but wanted to know what is the
general thinking on this.

Is debugging pl/pgsq a generic feature of PostgreSQL core considering
that pl/pgsql itself kind of is ?

Should there be something similar for debugging plain SQL and possibly
other PL languages?

Should there perhaps be debugging support in psql ?

------
Hannu

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Koval 2025-02-13 17:08:26 Assignment before assert
Previous Message Ranier Vilela 2025-02-13 16:59:17 Re: pg17.3 PQescapeIdentifier() ignores len