[go-nuts] Panic when highly concurrent MySQL queries

2017-02-16 Thread Dave Cheney
Can you share that code, it looks like you haven't checked the error from the previous call. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr

Re: [go-nuts] Panic when highly concurrent MySQL queries

2017-02-16 Thread lee
Ah thanks I had not seen this and replacing it with a non prepared version and some manual sql statement generation fixed the problem. Thank you! On Thursday, February 16, 2017 at 6:22:27 PM UTC, Justin Israel wrote: > > > > On Fri, Feb 17, 2017, 6:48 AM > wrote: > >> I have a channel that recei

Re: [go-nuts] Panic when highly concurrent MySQL queries

2017-02-16 Thread Justin Israel
On Fri, Feb 17, 2017, 6:48 AM wrote: > I have a channel that receives a lot of data that needs to be stored into > MySQL. > > After a short period of time I get the following... > > Error 1461: Can't create more than max_prepared_stmt_count statements > (current value: 16382) > panic: runtime err

[go-nuts] Panic when highly concurrent MySQL queries

2017-02-16 Thread lee
I have a channel that receives a lot of data that needs to be stored into MySQL. After a short period of time I get the following... Error 1461: Can't create more than max_prepared_stmt_count statements (current value: 16382) panic: runtime error: invalid memory address or nil pointer dereferen