-
Notifications
You must be signed in to change notification settings - Fork 2
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
Signals and the haskell runtime #3
Comments
I turned off signal handlers by passing the RTS the It looks like I should have also added |
I ran |
Without
With
The syscalls involving
This is Postgres v14, PL/Haskell 1.0, Ubuntu 22.04.1 on x86_64. |
I haven't looked deeply into this, but on my platform (x86_64 ubuntu 22.04), based on output of
strace -p $PID -e signal
, it seems thatplhaskell
makes some changes related to signals due to the haskell runtime.I see calls to
rt_sigaction
,rt_sigreturn
, andrt_sigprocmask
involvingSIGVTALRM
andSIGURG
. It seems that Postgres doesn't useSIGVTARLM
, but it does seem to useSIGURG
for latches. I'm slightly worried that there are edge cases where a plhaskell function can end up interfering with Postgres.Is there a way to get the haskell runtime to not mess with the signal handlers?
The text was updated successfully, but these errors were encountered: