next query after KILL QUERY will error
Bug #663919 reported by
Andrew Hutchings
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Fix Released
|
Medium
|
Andrew Hutchings | ||
| 7.0 |
Fix Released
|
Medium
|
Andrew Hutchings | ||
Bug Description
drizzle> select * from t1 order by b;
(t1 has 205,000 rows)
CTRL-C
drizzle> explain select * from t1 order by b;
ERROR 3 (HY000): Error reading file '%-.200s' (errno: %d)
All is fine for any query after this.
Related branches
lp://staging/~linuxjedi/drizzle/trunk-bug-663919
- Drizzle Developers: Pending requested
-
Diff: 13 lines (+3/-0)1 file modifieddrizzled/session.cc (+3/-0)
| summary: |
- second query after a ctrl-c will error + next query after a ctrl-c will error |
Revision history for this message
| Andrew Hutchings (linuxjedi) wrote Re: next query after a ctrl-c will error | #1 |
| Changed in drizzle: | |
| assignee: | nobody → Andrew Hutchings (linuxjedi) |
| Changed in drizzle: | |
| importance: | Undecided → Medium |
| summary: |
- next query after a ctrl-c will error + next query after KILL QUERY will error |
Revision history for this message
| Andrew Hutchings (linuxjedi) wrote | #2 |
To post a comment you must log in.
When looking at drizzled in GDB, this happens on CTRL-C:
[New Thread 0x7fffde7fc710 (LWP 4902)]
[Thread 0x7fffde7fc710 (LWP 4902) exited]
I'm guessing that is some client connection thread which is somehow spawned and instantly killed.