It seems PostgreSQL instances does not provide logs which is awefull for debug

Troubleshooting and help
,
1

I cannot find a way to have access to logs from my Koyeb Postgresql instance. I have a query that works on any other db but fails here and I cannot investigate…

Here is the output of some logs related queries which shows the logs cannot easily be accessed by the user:

SHOW log_destination;
SHOW logging_collector;
SHOW log_directory;
SHOW log_filename;
 log_destination 
-----------------
 stderr
(1 row)

 logging_collector 
-------------------
 off
(1 row)

 log_directory 
---------------
 log
(1 row)

          log_filename          
--------------------------------
 postgresql-%Y-%m-%d_%H%M%S.log
(1 row)

Any help on this one ?

The issue I encounter is the following:

(Background on this error at: https://sqlalche.me/e/20/e3q8)
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/sqlalchemy/engine/base.py", line 1964, in _exec_single_context
    self.dialect.do_execute(
  File "/usr/local/lib/python3.11/site-packages/sqlalchemy/engine/default.py", line 942, in do_execute
    cursor.execute(statement, parameters)
psycopg2.OperationalError: SSL connection has been closed unexpectedly

While the queries work perfectly well when connected through psql, it does not work when the session is idle for too long on my Koyeb Small Web instance.

I cannot debug it with PostgreSQL which is a real pain in the ass.

2

It is most probably due to the fact that your database scale to zero automatically after 5 minutes of inactivity.

We have it in our backlog and you can upvote for it: Postgres scale-to-zero configuration | Voters | Koyeb