You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running tests on ubuntu-24.04, sometimes the test_misc.py::test_options_startup_param test fails with the error "FATAL: client sent partial pkt in startup phase"
reproduce:
If you increase tcp_socket_buffer from 4096 to 8192, the error is not reproduced.
bouncer.ini
[databases]
postgres = port=5432 host=127.0.0.1 dbname=postgres user=postgres pool_size=2
[pgbouncer]
logfile = test.log
pidfile = test.pid
listen_addr = 127.0.0.1
listen_port = 15432
unix_socket_dir = /tmp
auth_type = trust
auth_file = userlist.txt
pool_mode = statement
; use a small tcp_socket_buffer so that we trigger EAGAIN more often in tests.
; Otherwise bugs caused by EAGAIN are hard to debug.
tcp_socket_buffer = 4096
The text was updated successfully, but these errors were encountered:
JelteF
added a commit
to JelteF/pgbouncer
that referenced
this issue
Apr 29, 2024
We were bailing out from a connection if we did not receive the full
startup packet in one go, or if it didn't fit in pkt_buf. This fixes
these issues by reusing the packet buffering logic that was introduced
for prepared statement support for our startup packet parsing.
Fixespgbouncer#1056
We were bailing out from a connection if we did not receive the full
startup packet in one go, or if it didn't fit in pkt_buf. This fixes
these issues by reusing the packet buffering logic that was introduced
for prepared statement support for our startup packet parsing.
Fixes#1056
When running tests on ubuntu-24.04, sometimes the test_misc.py::test_options_startup_param test fails with the error "FATAL: client sent partial pkt in startup phase"
reproduce:
If you increase tcp_socket_buffer from 4096 to 8192, the error is not reproduced.
bouncer.ini
The text was updated successfully, but these errors were encountered: