-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
🐛 Postgres Destination fails when the connection is persisted across steps #39365
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@kikoncuo please sign the CLA and update the title and description to match guidelines. |
...postgres/src/main/java/io/airbyte/integrations/destination/postgres/PostgresDestination.java
Show resolved
Hide resolved
Done! |
…hat already exists
@kikoncuo - just curious, which version/pass offering of postgres are you using that you saw this bug? |
@evantahler I'm using a new default supabase project which uses Postgres version 15.1.1.58 I also tried with an older project from a month ago which I successfully used to do multiple syncs, same problem. |
What
#39364
When using PostgreSQL as a destination, we tried to recreate a postgreSQL function which leads to an SQL error which crashes the sync process.
How
We've modified the SQL query to either create or replace the function, not only create which would lead to an error if the function already existed
Review guide
Try to use PostgreSQL as a destination with any source
User Impact
The function may re-created the function when it's not needed, but this shouldn't happen anyway as it's only on the session, in case other errors happen related to re-using the session, this would not crash the connector
Can this PR be safely reverted and rolled back?