On Tue, Jan 25, 2011 at 4:42 AM, Davi Arnaut <davi.arnaut@stripped> wrote:
> Hi Tor,
>
>
> On 1/19/11 4:49 PM, Tor Didriksen wrote:
>
>> #At file:///export/home/didrik/repo/trunk-sortaborted/ based on
>> revid:bar@stripped
>>
>> 3535 Tor Didriksen 2011-01-19
>> Bug #36022 please log more information about "Sort aborted" queries
>>
>> Write an additional warning message to the server log,
>> explaining why a sort operation is aborted.
>>
>> The output in mysqld.err will look something like:
>> [ERROR] bin-dbg/sql/mysqld: Sort aborted
>> [Warning] Sort aborted : Out of memory (Needed 24 bytes)
>>
>
> Why not include the reason in the error message itself?
I didn't dare to :-)
I thought maybe error messages were part of a documented interface,
and as such should be kept stable.
If you say I can change it, then of course.
-- didrik
>
>
> [ERROR] bin-dbg/sql/mysqld: Out of sort memory; increase server sort
>> buffer size
>> [ERROR] bin-dbg/sql/mysqld: Sort aborted
>> [Warning] Sort aborted : Out of sort memory; increase server sort
>> buffer size
>> [ERROR] bin-dbg/sql/mysqld: Sort aborted
>> [Warning] Sort aborted : Incorrect number of arguments for FUNCTION
>> test.f1; expected 0, got 1
>>
>> If --log-warn=2 is enabled, we output information about
>> host/user/query as well.
>>
>
> Whereas this additional information (host/user...) is fine in a warning.
>
> Regards,
>
> Davi
>
> --
> MySQL Code Commits Mailing List
> For list archives: http://lists.mysql.com/commits
> To unsubscribe:
> http://lists.mysql.com/commits?unsub=1
>
>
