You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this is an FYI. i tried to investigate it and couldn't find anything obvious; i think this is subtle problem with default Dialer for "unix" sockets. i don't have time to look into it further but thought someone here might want to know about it.
i used godrv for a project which has since been changed to use go-mysql-driver. there was an issue where go routines that access the database in a long running application would get stuck after a few days. the application uses one database connection, which is a unix domain socket. the application is a data logger that gets data from several systems once a day. usually by the third day the stuck condition would appear without any error or warning messages whatsoever. after switching to go-mysql-driver (i.e. switching the package import and the DSN format) i noticed that it is detecting a broken pipe condition during some writes, from which it recovers. I suspect the path that handles the default dialer for unix sockets in mymysql isn't doing the right thing.
sorry for the sketchy problem reporting.
The text was updated successfully, but these errors were encountered:
this is an FYI. i tried to investigate it and couldn't find anything obvious; i think this is subtle problem with default Dialer for "unix" sockets. i don't have time to look into it further but thought someone here might want to know about it.
i used godrv for a project which has since been changed to use go-mysql-driver. there was an issue where go routines that access the database in a long running application would get stuck after a few days. the application uses one database connection, which is a unix domain socket. the application is a data logger that gets data from several systems once a day. usually by the third day the stuck condition would appear without any error or warning messages whatsoever. after switching to go-mysql-driver (i.e. switching the package import and the DSN format) i noticed that it is detecting a broken pipe condition during some writes, from which it recovers. I suspect the path that handles the default dialer for unix sockets in mymysql isn't doing the right thing.
sorry for the sketchy problem reporting.
The text was updated successfully, but these errors were encountered: