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
Describe the bug
When a server address is marked bad a line is logged but it does not contain the error or reason for marking it bad. This is a bug because it makes it very difficult to troubleshoot why our connections are breaking in production. Upstream from pgcat the client appears to receive a "connection reset by peer" error but we are unable to track down the specific error.
To Reproduce
Steps to reproduce the behavior:
Do something that triggers an error in the connection
See the "marked bad" log line
Observe that there is no line for the actual error that occurred
Expected behavior
The logged line should include at least a mention of the error.
The text was updated successfully, but these errors were encountered:
Describe the bug
When a server address is marked bad a line is logged but it does not contain the error or reason for marking it bad. This is a bug because it makes it very difficult to troubleshoot why our connections are breaking in production. Upstream from pgcat the client appears to receive a "connection reset by peer" error but we are unable to track down the specific error.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The logged line should include at least a mention of the error.
The text was updated successfully, but these errors were encountered: