-
Notifications
You must be signed in to change notification settings - Fork 916
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
[Bug]: SEGFAULT when using COPY together with pgaudit extension #7667
Comments
Hi, I would also like to add that newer TimescaleDB (2.18.0) version fails with segfault even when using
|
Hi @TinT1, Thanks for the bug report! I was able to reproduce it. The issue here is that both timescaledb and pgaudit are using the ExecutorStart hook, and normally the calls should be chained, but it doesn't happen here. I'm working on a fix. |
Hi @zilder Unfortunately, we are still encountering the same issue after upgrading to TimescaleDB 2.18.2, which should include the fix for #7712 . I was able to reproduce the issue using the same steps, but with the Should we reopen the ticket? Did you manage to reproduce on 2.18.2 ? Thanks. gdb log
|
What type of bug is this?
Crash
What subsystems and features are affected?
Query executor, Platform/OS
What happened?
We are operating TimescaleDB (2.17.2) in Kubernetes and we noticed segfaults when using COPY command on hypertable with pgaudit (17.0) enabled.
You can find logs and steps to reproduce below.
Thank you
TimescaleDB version affected
2.17.2
PostgreSQL version used
17.2
What operating system did you use?
Ubuntu 22.04.5 LTS
What installation method did you use?
Docker
What platform did you run on?
On prem/Self-hosted
Relevant log output and stack trace
How can we reproduce the bug?
The text was updated successfully, but these errors were encountered: