New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
quickdie may be invoked on rxThread #11006
Comments
Should modify in |
Then we should add
In theory, this issue always exists, but it is difficult to trigger.
I don't know too |
If we mask all we should do that in |
It seems that we should and it is safe to mask all signal in the udp pthreads. Please feel free to open a PR. |
ok, I will submit a PR today
|
In some cases, some signals (like SIGQUIT) that should only be processed by the main thread of the postmaster may be dispatched to rxThread. So we should and it is safe to block all signals in the udp pthreads. Fix greenplum-db#11006
In some cases, some signals (like SIGQUIT) that should only be processed by the main thread of the postmaster may be dispatched to rxThread. So we should and it is safe to block all signals in the udp pthreads. Fix #11006
In some cases, some signals (like SIGQUIT) that should only be processed by the main thread of the postmaster may be dispatched to rxThread. So we should and it is safe to block all signals in the udp pthreads. Fix greenplum-db#11006 (cherry picked from commit 54451fc)
Greenplum version or build
OS version and uname -a
autoconf options used ( config.status --config )
Installation information ( pg_config )
Actual behavior
Step to reproduce the behavior
On the 8C32G machine, this can always reproduce the error. If your machine has a higher configuration, then increase the number of clients.
This error can be fixed with some patch as follow:
The text was updated successfully, but these errors were encountered: