- Notifications
You must be signed in to change notification settings - Fork328
Added pyarrow==11.0.0 to requirements to solve postgres segfault#1182
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
…ould segfault after a client session which used pgml command closes. The issue can be identified in postgres log files with the line 'arrow::fs::FinalizeS3 was not called even though S3 was initialized. This could lead to a segmentation fault at exit'
Ryangr0 commentedNov 23, 2023
How is it possible that all of a sudden I'm running into this issue? Super strange. |
I had this problem as well with a previous version on pg15 however there it happens only sparingly. I recently did a new install with pg16 and then it started happening on every connection to the DB where I made a pgml.embed query. |
Thanks for the fix! |
stuta commentedAug 30, 2024
In OSX M1/M3 pyarrow 11 does not compile. |
Added pyarrow==11.0.0 to requirements to solve issue where postgres would segfault after a client session which used pgml command closes. The issue can be identified in postgres log files with the line 'arrow::fs::FinalizeS3 was not called even though S3 was initialized. This could lead to a segmentation fault at exit'
Same issue as shown here:AlUlkesh/stable-diffusion-webui-images-browser#216