On Sat, Jun 11, 2016 at 2:07 PM, Andreas Seltenreich <seltenre...@gmx.de>
> Amit Kapila writes:
> > I have moved it to CLOSE_WAIT state because we have derived our
> > queries to reproduce the problem based on original report. If next
> > run of sqlsmith doesn't show any problem in this context then we will
> > move it to resolved.
> I don't have access to my testing horse power this weekend so I can
> report on tuesday at the earliest. Unless someone else feels like
> running sqlsmith…
No issues and many thanks for testing.