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
Hello:
I noticed the following lines in my PostgreSQL log file today:
2022-12-01 14:16:54.517 UTC [10073] ERROR: cannot commit while a portal is
pinned
2022-12-01 14:16:54.517 UTC [10073] STATEMENT: call p_annotate_db_stats()
The process ID can be traced to plpython procedure call.
What is
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:
Hello:
Below is a sample case that exhibits a behavior that I can't explain:
-- create the table
create table ts (t timestamp without time zone);
-- populate
insert into ts(t) values ('2022-07-16 00:22:06.974000');
insert into ts(t) values ('2022-07-16 00:22:06.974000');
insert into ts(t) values
On Friday, July 8, 2022 at 10:20:52 PM GMT+8, Tom Lane
wrote:
Ludwig Isaac Lim writes:
>> Hello:
>> I noticed that I'm getting errors when copy and pasting code for stored
>> procedure from Windows directly into psql running in putty.
>> To reproduc
Hello:
I noticed that I'm getting errors when copy and pasting code for stored
procedure from Windows directly into psql running in putty.
To reproduce create a procedure that has multiple statements with each
statements having multiple lines, similar to the ones below:
CREATE OR REPLACE PROCEDUR
> On Thursday, February 10, 2022, 01:49:10 AM GMT+8, Tom Lane
> wrote:
>> Ludwig Isaac Lim writes:
>> How do make sure that NIC will be listening every time I started/restarted
>> the server?
> You need to tell systemd not to start the postgresql servic
Hello:
I'm running postgresql 12.9 on Amazon Linux in AWS.
My listen_addresses in postgresql.conf is configured like below:
listen_addresses = '172.17.1.57,localhost'
However, postgresql does not listen on 172..17.1.57. I can reproduce the
phenomenon by simply rebooting the server and then r
