-
Notifications
You must be signed in to change notification settings - Fork 23
Skip event triggers in pg_dump v16 #627
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
Skip event triggers in pg_dump v16 #627
Conversation
|
This is my first contribution to postgres code. Can't figure out why I get segfaults for specific tests 🤔 |
|
In you are getting segfaults, run the command you are using to test in a debugger: And when it fails, enter the command |
|
Weird. There are no |
a576391 to
082025e
Compare
1a9c49d to
a7505f8
Compare
a7505f8 to
2a1ebf7
Compare
|
Ready to merge |
## Problem Data import fails if the src db has any event triggers, because those can only be restored by a superuser. Specifically imports from Heroku and Supabase are guaranteed to fail. Closes https://github.com/neondatabase/cloud/issues/27353 ## Summary of changes Depends on `pg_dump` patches per each supported PostgreSQL version: - neondatabase/postgres#630 - neondatabase/postgres#629 - neondatabase/postgres#627 - neondatabase/postgres#628
https://github.com/neondatabase/cloud/issues/27353