MIME-Version: 1.0
References: <46505a4b-517b-0967-c2f9-1364a794ecef@thomas-guettler.de>
In-Reply-To: <46505a4b-517b-0967-c2f9-1364a794ecef@thomas-guettler.de>
From: Daniele Varrazzo <daniele.varrazzo@gmail.com>
Date: Mon, 20 May 2019 19:19:24 +0900
Message-ID: 
 <CA+mi_8a5rij_5xchPkYPFS3moAtw9i6TrwKndynWfbJ=kFA4fg@mail.gmail.com>
Subject: Re: Log Stacktrace of current Python Interpreter via PostgreSQL
 trigger
To: =?UTF-8?Q?Thomas_G=C3=BCttler?= <guettliml@thomas-guettler.de>
Cc: psycopg@postgresql.org
Content-Type: multipart/alternative; boundary="000000000000b5500505894f11f9"
Precedence: bulk

--000000000000b5500505894f11f9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

If you use postgres logging in stored procedures you can retrieve the logs
in 'connection.notices'.

http://initd.org/psycopg/docs/connection.html#connection.notices

On Mon, 20 May 2019, 16:40 Thomas G=C3=BCttler, <guettliml@thomas-guettler.=
de>
wrote:

> I am hunting a non reproducible in a production environment.
>
> I can detect the buggy change in a postgres trigger.
>
> Since it is production code I must no raise an exception. I can
> only use logging.
>
> If I could see the stacktrace of the python interpreter, I could
> see which codes the change which I am hunting.
>
> But how to get this interpreter stacktrace, if the condition is
> detect in the db trigger?
>
>
>
> https://stackoverflow.com/questions/51873708/log-stacktrace-of-python-in-=
postgresql-trigger
>
> Maybe there is a psycopg2 feature which I don't know up to now.
>
> I guess LISTEN+NOTIFY could get used.
> Or setting a connection variable which I check after each SQL statement.
>
> Ideas welcome,
>
>    Thomas G=C3=BCttler
>
>
> --
> Thomas Guettler http://www.thomas-guettler.de/
> I am looking for feedback:
> https://github.com/guettli/programming-guidelines
>
>
>

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

<div dir=3D"auto">If you use postgres logging in stored procedures you can =
retrieve the logs in &#39;connection.notices&#39;.<div dir=3D"auto"><br></d=
iv><div dir=3D"auto"><a href=3D"http://initd.org/psycopg/docs/connection.ht=
ml#connection.notices">http://initd.org/psycopg/docs/connection.html#connec=
tion.notices</a><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">On Mon, 20 May 2019, 16:40 Thomas G=C3=BCttler, &=
lt;<a href=3D"mailto:guettliml@thomas-guettler.de">guettliml@thomas-guettle=
r.de</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I am hunting a =
non reproducible in a production environment.<br>
<br>
I can detect the buggy change in a postgres trigger.<br>
<br>
Since it is production code I must no raise an exception. I can<br>
only use logging.<br>
<br>
If I could see the stacktrace of the python interpreter, I could<br>
see which codes the change which I am hunting.<br>
<br>
But how to get this interpreter stacktrace, if the condition is<br>
detect in the db trigger?<br>
<br>
<br>
<a href=3D"https://stackoverflow.com/questions/51873708/log-stacktrace-of-p=
ython-in-postgresql-trigger" rel=3D"noreferrer noreferrer" target=3D"_blank=
">https://stackoverflow.com/questions/51873708/log-stacktrace-of-python-in-=
postgresql-trigger</a><br>
<br>
Maybe there is a psycopg2 feature which I don&#39;t know up to now.<br>
<br>
I guess LISTEN+NOTIFY could get used.<br>
Or setting a connection variable which I check after each SQL statement.<br=
>
<br>
Ideas welcome,<br>
<br>
=C2=A0 =C2=A0Thomas G=C3=BCttler<br>
<br>
<br>
-- <br>
Thomas Guettler <a href=3D"http://www.thomas-guettler.de/" rel=3D"noreferre=
r noreferrer" target=3D"_blank">http://www.thomas-guettler.de/</a><br>
I am looking for feedback: <a href=3D"https://github.com/guettli/programmin=
g-guidelines" rel=3D"noreferrer noreferrer" target=3D"_blank">https://githu=
b.com/guettli/programming-guidelines</a><br>
<br>
<br>
</blockquote></div>

--000000000000b5500505894f11f9--