After terminating session file has been updated with new lines.
***content from the previous letter***
***That one unfinished line. Freeze for ~6 hours.***
epoll_wait(4, 0x555d738e4f30, 1, -1) = -1 EINTR (Interrupted system call)
<21328.371590>
--- SIGTERM {si_signo=SIGTERM, si_code=SI_USE
I was able to connect to this process using
strace -T -p `pgrep -n -u ks-postgres -f "ocb.*FETCH"` -o
strace_of_active_session -ff
(the -T flag gives us the time the system call has been running at the end of
each line).
If the session had been hanging active for some time, there was only on
Magnus,
PostgreSQL 14.6 on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6)
10.2.1 20210110, 64-bit
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
It is docker container if it matters and yep, possibly slow and unreliable
network also is an issue.
So you're assuming the statement_tim
On Tue, Mar 26, 2024 at 3:19 PM Ц wrote:
> Greetings!
> I’ve faced with strange behavior when I see a lot of active sessions
> started hours ago while statement_timeout = '30min'.
> All of them are fetching from cursors.
>
> Typical session looks like:
> backend_start| 2024-03-26 14:34:20.552
Greetings!
I’ve faced with strange behavior when I see a lot of active sessions started
hours ago while statement_timeout = '30min'.
All of them are fetching from cursors.
Typical session looks like:
backend_start | 2024-03-26 14:34:20.552594+03
xact_start | 2024-03-26 14:34:54.974
