pending client won't wake up when using prepared statement #12
Comments
|
Thank you for reporting the problem. |
|
it's ok now. |
knizhnik
pushed a commit
that referenced
this issue
Mar 21, 2021
Test #12 overwrote a 1-byte varlena header to make it look like the initial byte of a 4-byte varlena header, but the results were endian-dependent. Also, the byte "abc" that followed the overwritten byte would be interpreted differently depending on endian-ness. Overwrite 4 bytes instead, in an endian-aware manner. Test #13 accidentally managed to depend on TOAST_MAX_CHUNK_SIZE, which varies slightly depending on MAXIMUM_ALIGNOF. That's not the point anyway, so make the regexp insensitive to the expected number of chunks. Mark Dilger Discussion: http://postgr.es/m/[email protected]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'm testing builtin-pool.
The problem is channel_read() function of proxy.c.
When using prepared statement, a message contains multiple commands, for example, "Parse", "Bind" ... . If a client execute prepared statement and wait for free backend, on condition "Backend was not assigned", only the first command , for example ,"Parse" will be sent when pending client is served.
therefore, the backend is waiting for next command from client , and client is waiting for the respond from backend.
The text was updated successfully, but these errors were encountered: