MIME-Version: 1.0
From: James Creasy <james@buildtrue.io>
Date: Thu, 8 Aug 2024 10:15:33 -0700
Message-ID: <CADN1ADdP5QrUqkMUDQAANnnajZkusp8+EEo-U8d8qto9=iv=vQ@mail.gmail.com>
Subject: Debugging set up for Postgres?
To: pgsql-general@postgresql.org
Content-Type: multipart/alternative; boundary="0000000000008d7df1061f2f2d1f"
Archived-At: <https://www.postgresql.org/message-id/CADN1ADdP5QrUqkMUDQAANnnajZkusp8%2BEEo-U8d8qto9%3Div%3DvQ%40mail.gmail.com>
Precedence: bulk

--0000000000008d7df1061f2f2d1f
Content-Type: text/plain; charset="UTF-8"

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?

Thanks for reading,

James

--0000000000008d7df1061f2f2d1f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>We&#39;ve spent about 12 hours =
trying to set up a working debugger for psql functions without success, try=
ing both PGAdmin 4 v8.3 and DBeaver.=C2=A0</div><div><br></div><div>The onl=
ine searches turn up multiple instructions for Postgres 12 or older, howeve=
r we are using 16. Our extensions include PostGIS and supporting extensions=
 like SFCGAL.=C2=A0</div><div><br></div><div>We can get the PGAdmin debugge=
r to stop at a breakpoint, but as soon as it exits a function, PGAdmin cras=
hes (&quot;error when executing continue&quot;) and has to be restarted.=C2=
=A0</div><div><br></div><div>We also tried direct debugging, but the inputs=
 to our functions are often json objects, and there isn&#39;t a way to past=
e such an object into the Value field.</div><div><br></div><div>My question=
 is: is there a way to effectively step debug psql functions in Postgres 16=
 and how?=C2=A0</div><div><br></div><div>Thanks for reading,</div><div><br>=
</div><div>James</div></div>

--0000000000008d7df1061f2f2d1f--