public inbox for [email protected]
help / color / mirror / Atom feedFrom: Pavel Stehule <[email protected]>
To: James Creasy <[email protected]>
Cc: [email protected]
Subject: Re: Debugging set up for Postgres?
Date: Thu, 8 Aug 2024 19:40:29 +0200
Message-ID: <CAFj8pRCGzCu_SN45K+wvOs+npAN6nN3qhb5VJW-tqXX-mhVp_w@mail.gmail.com> (raw)
In-Reply-To: <CADN1ADdP5QrUqkMUDQAANnnajZkusp8+EEo-U8d8qto9=iv=vQ@mail.gmail.com>
References: <CADN1ADdP5QrUqkMUDQAANnnajZkusp8+EEo-U8d8qto9=iv=vQ@mail.gmail.com>
Hi
čt 8. 8. 2024 v 19:16 odesílatel James Creasy <[email protected]> napsal:
> Hi all,
>
> We've spent about 12 hours trying to set up a working debugger for psql
> functions without success, trying both PGAdmin 4 v8.3 and DBeaver.
>
> The online searches turn up multiple instructions for Postgres 12 or
> older, however we are using 16. Our extensions include PostGIS and
> supporting extensions like SFCGAL.
>
> We can get the PGAdmin debugger to stop at a breakpoint, but as soon as it
> exits a function, PGAdmin crashes ("error when executing continue") and has
> to be restarted.
>
> We also tried direct debugging, but the inputs to our functions are often
> json objects, and there isn't a way to paste such an object into the Value
> field.
>
> My question is: is there a way to effectively step debug psql functions in
> Postgres 16 and how?
>
Do you think plpgsql functions?
There should not be any change if I know - you need to use PLdebugger
extension, and then you can use plpgsql debugger.
Maybe you use more extensions that use plpgsql debug API in one moment -
plprofiler, or plpgsql_check. This is not supported (plpgsql_check is
exception, but it should be loaded last).
Regards
Pavel
>
> Thanks for reading,
>
> James
>
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Debugging set up for Postgres?
In-Reply-To: <CAFj8pRCGzCu_SN45K+wvOs+npAN6nN3qhb5VJW-tqXX-mhVp_w@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox