Hi, mysql 5.7 bumped soname of the libmysqlclient.so. Are there any
plans to do something like that in mariadb's libmysqlclient.so?
I'm also wondering whether there are any particular plans to keep
compatibility of the client library (libmysqlclient.so) between MariaDB
and MySQL in the future.
This is just a re-sending the issue reported already at
https://mariadb.atlassian.net/browse/MDEV-6870 to make it more visible,
since there is no respond yet.
There was an issue [1] in mysql and mariadb prior to 5.5.40 if socket or
fifo files were used as general_log and slow query log files.
On 09/04/2014 05:17 PM, Sergei Golubchik wrote:
Hi, Honza!
On Sep 03, Honza Horak wrote:
in Fedora, we're about to package mariadb-native-client, which we'd like
to utilize in Fedora as much as possible since using this piece of
software we can break the dependency on whole mari
Hi,
in Fedora, we're about to package mariadb-native-client, which we'd like
to utilize in Fedora as much as possible since using this piece of
software we can break the dependency on whole mariadb server package and
thus make the base system more compact.
However, since mariadb.org does not
On 06/12/2014 05:08 PM, Sergei Golubchik wrote:
Hi, Honza!
there are apparently some tools out there [1], that check if the server
is up quite often, while not closing the connection properly. It
eventually ends in 'many connection errors', because max_connect_errors
is always limited now.
[1]
Hi guys,
there are apparently some tools out there [1], that check if the server
is up quite often, while not closing the connection properly. It
eventually ends in 'many connection errors', because max_connect_errors
is always limited now.
I understand that this way of checking may be wrong
On 04/07/2014 08:36 PM, Sergei Golubchik wrote:
Hi, Honza!
On Apr 07, Honza Horak wrote:
Hi guys,
first, congratulations for the 10.0 release, well done!
Thanks!
Even though it can look insane, I'm already wondering about next minor
releases ;) Especially if you have already some
Hi guys,
first, congratulations for the 10.0 release, well done!
Even though it can look insane, I'm already wondering about next minor
releases ;) Especially if you have already some idea about 10.1 and later.
Specifically, I'm wondering if these releases will still be somehow
tight to MySQ
Thanks for your quick answers, guys, very appreciated.
Regards,
Honza
On 01/21/2014 03:31 PM, Michael Widenius wrote:
Hi!
"Honza" == Honza Horak writes:
Honza> Hi guys,
Honza> I'm not able to find any information about compatibility assurance of
Honza> server side
Hi guys,
I'm not able to find any information about compatibility assurance of
server side -- i.e plugin interface and libmysqld.so library. I expect
both should have stable API at least for one minor version across bugfix
releases, but I don't believe that libmysqld.so is able to preserve ABI
On 01/08/2014 06:10 PM, Sergei Golubchik wrote:
Hi, Honza!
On Jan 08, Honza Horak wrote:
* change the versioning to be correct and debian-compatible,
by having old symbols to appear under both libmysqlclient_16 and
libmysqlclient_18 version.
I don't believe Debian will use F
On 01/08/2014 06:10 PM, Sergei Golubchik wrote:
Hi, Honza!
On Jan 08, Honza Horak wrote:
* change the versioning to be correct and debian-compatible,
by having old symbols to appear under both libmysqlclient_16 and
libmysqlclient_18 version.
I don't believe Debian will use F
On 01/08/2014 02:25 PM, Sergei Golubchik wrote:
Hi, Honza!
On Jan 07, Sergei Golubchik wrote:
On Jan 07, Honza Horak wrote:
Primarily, I'd like to hear what MariaDB upstream's position on that
is, if the sync can happen, but any ideas will be welcome.
I believe, Fedora's way
Hi guys,
I'm writing this as a maintainer of MariaDB package in Fedora and RHEL.
I've got some complaints about libmysqlclient symbols versioning in
Fedora and future RHEL-7:
https://bugzilla.redhat.com/show_bug.cgi?id=1045013
Simply put, the issue there is that RPMs (both made by MariaDB ups
Hi guys,
quite tricky problem came up after a directory has been created by
something else than mysqld in the datadir.
Suppose we use datadir=/var/lib/mysql. When we create any file in that
directory by hand (or some program does it, which is not just
imagination, it really happens), e.g. /v
On 08/13/2013 06:20 PM, Honza Horak wrote:
On 08/13/2013 12:51 PM, Michael Widenius wrote:
Hi!
"Honza" == Honza Horak writes:
Honza> Hi guys,
Honza> maybe I just need some little kick or I should get a coffee,
but I can't
Honza> understand the following config
On 08/13/2013 12:51 PM, Michael Widenius wrote:
Hi!
"Honza" == Honza Horak writes:
Honza> Hi guys,
Honza> maybe I just need some little kick or I should get a coffee, but I can't
Honza> understand the following config file ordering difference.
Honza> Reading [1]
Hi guys,
maybe I just need some little kick or I should get a coffee, but I can't
understand the following config file ordering difference.
Reading [1] and code in mariadb-5.5.32/mysys/default.c:1226, it looks
like expected order of config files in Linux should be:
/etc/my.cnf /etc/mysql/my
Hi Guys,
since 10.x won't be compatible with mysql in every aspect any more, I'm
wondering if there happen to be any plans to move all compatibility
left-overs (client binary names, client library name, daemon binary
name, etc.). Are there any such ideas?
I understand that we would lose the
On 05/24/2013 11:04 PM, Rasmus Johansson wrote:
Hi,
On Tue, May 14, 2013 at 5:57 PM, Honza Horak mailto:hho...@redhat.com>> wrote:
Hi guys,
I'm not able to find any info about life cycle of MariaDB 5.5 or
even other versions. Particularly if the MariaDB 5.5 life
Hi guys,
I'm not able to find any info about life cycle of MariaDB 5.5 or even
other versions. Particularly if the MariaDB 5.5 life cycle will somehow
follow the MySQL's 5.5 life cycle or if there is some another
vision/rough plans when supporting of 5.5 will end?
Cheers,
Honza
Hi guys,
MariaDB forked mytop utility source some time back, but it causes some
issues for us in Fedora for example (and similarly in other
distributions I guess) -- particularly the MariaDB's binary mytop
conflicts with the same utility from separate package mytop. So, I'd
like to take a loo
45 PM, Honza Horak wrote:
Hi guys,
I failed to find the info in which versions of MariaDB "C API for
dynamic columns" is available as described here:
https://kb.askmonty.org/en/dynamic-columns-api/
I think the information should be the best included directly on the page
itself.
Hi guys,
I failed to find the info in which versions of MariaDB "C API for
dynamic columns" is available as described here:
https://kb.askmonty.org/en/dynamic-columns-api/
I think the information should be the best included directly on the page
itself.
Regards,
Honza
__
On 02/06/2013 09:33 PM, Sergei Golubchik wrote:
Hi, Honza!
On Feb 05, Honza Horak wrote:
Hi guys,
while we were packaging MariaDB into Fedora (finally) we used the
upstream's cnf files structure, which means /etc/my.cnf, that includes
all files from directory /etc/my.cnf.d/* using stat
This should have been posted better to maria-developers, probably, so
re-sending..
On 02/05/2013 01:55 PM, Honza Horak wrote:
Hi guys,
while we were packaging MariaDB into Fedora (finally) we used the
upstream's cnf files structure, which means /etc/my.cnf, that includes
all files
Hi all,
I've noticed that man page for mysql_plugin utility (man/mysql_plugin.1)
is not present in mariadb-5.5.28a.tar.gz while it is present in
mysql-5.5.28.tar.gz. However, I failed to find the reason why in case
there is one. Or is that a mistake? Does anybody know?
Regards,
Honza
__
27 matches
Mail list logo
