lidavidm commented on issue #1881: URL: https://github.com/apache/arrow-adbc/issues/1881#issuecomment-2129224545
Thanks. Interesting, there's occasional reference to errors like this elsewhere [1], but usually the suggestion is that something is port-scanning Postgres. That doesn't seem likely here. On the other hand, if the client were doing something wrong after a long time, restarting the client completely should presumably reset that. So instead it seems like something borks the server. Just to clarify, though: (1) Did you try restarting the Postgres server, too? (2) Did you restart the Postgres server and then try with SQLAlchemy? (3) If not, then it sounds like: using ADBC for a while borks the server, but using SQLAlchemy (without restarting the server) works, and it's unknown whether switching back to ADBC would fail or work? [1]: https://forum.strapi.io/t/strapi-server-when-deployed-using-docker-container-stops-with-errors-even-though-it-works-great-for/37994 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
