Neon integration with Inngest exhausted my compute branch quota
Hello, I have some trouble while integrating Neon with Inngest.
I followed the Neon & Inngest tutorial to connect both platforms.
I first connected to my production branch (main) and observed that the events were correctly published.
Then I removed the integration on Inngest's side to connect with my develop branch instead (as it does not seem like we can manage several connections on Inngest's side).
Since then I'm totally stuck :
- My compute quota for develop branch went out of control (I am currently on the free pricing) : even after disconnecting on Inngest's side it appears that a connection is hold and is preventing the develop db to auto-shutdown after 5 mins. I can't find a way to remove the connection or manually shutdown the DB (without removing the branch).
- I tried several times to reconnect with my production database but I can't, I can go with all the integration wizard process but then it just does not work and if I come back to the integration view on Inngest, it continues to propose to "Connect" instead of the "Manage" button that should show that Inngest is properly connected with Neon.
Any idea about what's going on ?
N.B: I might have misunderstood something as I am notan expert with Postgre WAL replication architecture.
2 Replies
rising-crimsonOP•7mo ago
I think I figured it out following Airbyte's tutorial : https://airbyte.com/data-engineering-resources/postgres-drop-replication-slot
For whoever might be interested, I managed it the following way :
- Get the connection string for "inngest" user on develop
- Connect to the DB with a Postgre client
- List the replication slots with : SELECT * FROM pg_replication_slots; (confirming that there was a dangling slot that was still active there)
- Killed the process with : SELECT pg_terminate_backend(active_pid_of_the_process>); (to make it inactive)
- Finally remove the replication slot : SELECT pg_drop_replication_slot('inngest_cdc');
- Remove the publication : DROP publication inngest
I can confirm that it closed the dangling connection.
How Do You Drop a Replication Slot in PostgreSQL? | Airbyte
Learn how to safely drop PostgreSQL replication slots using step-by-step procedures and best practices. A guide for database engineers covering active slot handling, troubleshooting, etc.
conscious-sapphire•7mo ago
Glad you got this sorted out, Chris, and thanks for sharing your solution.