On 12/13/22 13:20, Shaozhong SHI wrote:
What is brilliant about plpython? Any brilliant examples to look at?
1) It is actually plython(3)u where the u means untrusted. This means
you can reach outside the database and do things. That can seen as
brilliant or dangerous.
2) You have no end
What is brilliant about plpython? Any brilliant examples to look at?
On Friday, 2 December 2022, Ludwig Isaac Lim wrote:
> I'm having problems wherein my print() statements inside my plpython
> stored proc are not appearing in postgresql log. I tried setting the
> file=sys.stderr
>
> To reprodu
Hi Tom:
>> I'm having problems wherein my print() statements inside my plpython stored
>> proc are not appearing in postgresql log. I tried setting the file=sys.stderr
> Hmm. I can tell you that with "logging_collector = on", I would only expect
> the logs to capture stderr output, not s
Ludwig Isaac Lim writes:
> I'm having problems wherein my print() statements inside my plpython stored
> proc are not appearing in postgresql log. I tried setting the file=sys.stderr
Hmm. I can tell you that with "logging_collector = on", I would only
expect the logs to capture stderr output, n
I'm having problems wherein my print() statements inside my plpython stored
proc are not appearing in postgresql log. I tried setting the file=sys.stderr
To reproduce:
CREATE OR REPLACE PROCEDURE p_ludwig_test()
AS
$$
import sys
try:
x = 1 / 0
except:
