---
WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...: Efficient group commit for binary log
CREATION DATE..: Mon, 26 Apr 2010, 13:28
SUPERVISOR.:
---
WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...: Efficient group commit for binary log
CREATION DATE..: Mon, 26 Apr 2010, 13:28
SUPERVISOR.:
Hi Peter
On 12/05/2010, at 4:00 PM, Peter Zaitsev wrote:
5.2.47 is a lot more clear for me though it relays on the fact
MySQL chose not to release 5.2 themselves
What are you going to do with 5.5 as it comes out ? Create 5.6 and
hope MySQL will never release such a version ?
I think it is
Henrik,
5.2.47 is a lot more clear for me though it relays on the fact MySQL chose
not to release 5.2 themselves
What are you going to do with 5.5 as it comes out ? Create 5.6 and hope
MySQL will never release such a version ?
I think it is confusing.
I also think this is moving away from what
Monty,
For the latest MariaDB 5.2, all the fixes in the latest MariaDB 5.1
> are there.
>
This does not really help as one has to often check this a while ago.
Do you remember now what MySQL 5.0 bug fixes are included in MySQL 5.1.26
?
Finding what 5.0 version was last at that time and also ac
#At lp:maria/5.2 based on
revid:i...@askmonty.org-20100429211039-rp1mza3xjeqd4t1w
2789 Igor Babaev 2010-05-11
Fixed several bugs in the backport code (mwl#106).
modified:
mysql-test/r/innodb_lock_wait_timeout_1.result
mysql-test/r/lock_multi_bug38499.result
Hi Henrik, all
On 11/05/2010, at 10:52 PM, Henrik Ingo wrote:
On Tue, May 11, 2010 at 3:39 AM, Peter Zaitsev wrote:
Inventing your own MariaDB 5.2 is very confusing, seriously
Are fixes in MySQL 5.1.47 in MariaDB 5.2.0 ? Requirement to
go and
check the docs all the time is inconven
Hi!
> "Peter" == Peter Zaitsev writes:
Peter> Sergei,
Peter> I just wanted to mention product version and how it is encoded in RPM and
Peter> DEB packages are 2 different things.
Peter> We have similar problem with Percona Server, adding some unstable
features
Peter> and we plan to either
#At lp:maria/5.2
2758 kniel...@knielsen-hq.org 2010-05-11
Fix Windows ^M line ending.
modified:
sql/slave.h
=== modified file 'sql/slave.h'
--- a/sql/slave.h 2010-03-22 07:34:28 +
+++ b/sql/slave.h 2010-05-11 13:24:37 +
@@ -106,7 +106,7 @@ extern MYSQL_PL
Hi, Henrik!
On May 11, Henrik Ingo wrote:
> On Tue, May 11, 2010 at 12:05 PM, Sergei Golubchik wrote:
> >
> > we've talked about engine attributes in the CREATE TABLE, and that
> > one should be able to specify them per partition as well.
> >
> > Now, thinking about it, I'm not quite sure what th
On Tue, May 11, 2010 at 12:05 PM, Sergei Golubchik wrote:
> Hi,
>
> we've talked about engine attributes in the CREATE TABLE,
> and that one should be able to specify them per partition as well.
>
> Now, thinking about it, I'm not quite sure what the semantics shuld be.
>
> What is your use case ?
On Tue, May 11, 2010 at 3:39 AM, Peter Zaitsev wrote:
> Inventing your own MariaDB 5.2 is very confusing, seriously
>
> Are fixes in MySQL 5.1.47 in MariaDB 5.2.0 ? Requirement to go and
> check the docs all the time is inconvenient.
What you say here is a very good use case to check prop
Merge authors:
Kristian Nielsen (knielsen)
revno: 2854 [merge]
committer: kniel...@knielsen-hq.org
branch nick: mariadb-5.1
timestamp: Tue 2010-05-11 13:28:14 +0200
message:
Automerge MariaDB 5.1.44b into trunk.
modified:
configure.
Hi,
we've talked about engine attributes in the CREATE TABLE,
and that one should be able to specify them per partition as well.
Now, thinking about it, I'm not quite sure what the semantics shuld be.
What is your use case ? How do you want them to work ?
I see different possibilities. Say, the
14 matches
Mail list logo
