I don't use it in production, but this may change in the future. The problem is
that I cannot enable it when I need it, if I don't want to restart the server.
Regards
Federico
El mar, 3/6/14, Colin Charles escribió:
Asunto: [Maria-discuss] PERFORM
Hi, Sanja!
Please add in your revision a test case for MySQL bug#13919851
http://bazaar.launchpad.net/~mysql/mysql-server/5.6/revision/4514
and make sure that your fix doesn't break it.
On May 09, sa...@askmonty.org wrote:
> revno: 4207
> revision-id: sa...@askmonty.org-20140509104240-ksrk10tef
nice :) no problem
2014-06-03 16:00 GMT-03:00 Sergei Golubchik :
> Hi, Roberto!
>
> On Jun 03, Roberto Spadim wrote:
>> hi sergei, i think it's easy too
>> maybe we could have some kind of servers, one for debug, one for
>> production with instrumentations features and a clean server without
>> in
Hi, Roberto!
On Jun 03, Roberto Spadim wrote:
> hi sergei, i think it's easy too
> maybe we could have some kind of servers, one for debug, one for
> production with instrumentations features and a clean server without
> intrumentations, just an idea, i think some time ago mysql was
> releasing my
hi sergei, i think it's easy too
maybe we could have some kind of servers, one for debug, one for
production with instrumentations features and a clean server without
intrumentations, just an idea, i think some time ago mysql was
releasing mysql-dev, mysql-debug, mysql-xxx i'm wrong?
2014-06-03 14
Hi, Pavel!
On Jun 03, Pavel Ivanov wrote:
> I personally would prefer if MariaDB had performance schema not
> compiled in by default. Then we wouldn't be frustrated every time we
> upgrade and find out that the tarball doesn't compile without
> performance schema (yes, 10.0.11 doesn't compile).
T
hum, maybe a "-debug" package and a "-production" package could be better
if someone what a developer version get the -debug, for production use
"-production"
is it easy to create two kinds of packages at mariadb release time?
2014-06-03 14:10 GMT-03:00 Pavel Ivanov :
> I personally would prefer
Hi,
Never used it on production. From my point of view, it should be
disabled by default, but included.
The whole purpose of this variable is to have a way to analyze/optimize
performances easily, when needed; if it's enable by default, we have a
perf hit, so that's counterproductive.
I assu
Hi Sergei,
On 06/02/2014 07:10 PM, Sergei Golubchik wrote:
Hi, Alexander!
Looks ok to push, thanks!
Thanks for review!
One minor comment below.
an answer to your comment below:
On Jun 02, Alexander Barkov wrote:
=== modified file 'sql/field.h'
--- sql/field.h 2014-03-26 21:25:38 +0
Hello Sergei,
A few weeks ago we fixed this bug for 10.0 by changing temporal items
not to have decimals=NOT_FIXED_DEC (more MySQL-5.6 compatibility),
and agreed to have a separate patch for the pre-10.0 branches.
This patch is for 5.3 and 5.5 only.
It back-ports the mdev-4511 tests from 10.0
Hi all,
Recently there was chat about how PERFORMANCE_SCHEMA was enabled by mistake and
it should be disabled in the 10.0 series. I'm curious - how many of you are
using PERFORMANCE_SCHEMA? Is it a problem to turn it on, if you use it?
I'm referring to:
https://mariadb.atlassian.net/br
Hi,
It seems we have a POWER8 box and soon will start doing builds on this platform
Stewart Smith (currently at IBM) seems to be doing some work on MySQL 5.6 and
MySQL 5.7 for POWER8 systems - there doesn't seem to be much attention being
paid to MariaDB 10. Ideally, our fixes that are being pi
12 matches
Mail list logo
