On 02/11/2014 09:00 AM, seppo.jaak...@codership.com wrote:
Hi, I'll add $.02 more to this discussion.
Galera does not use the MySQL Pluggable Storage Engine Aarchitecture
(PSEA), because Galera needs, as pointed out by Justin, more interaction
with other storage engines (InnoDB currently, TokuDB
Thanks Sergei, that sounds great!
I'll keep an eye on that issue
Honza
On 02/12/2014 05:37 PM, Sergei Golubchik wrote:
Hi, Honza!
On Feb 11, Honza Horak wrote:
Hi guys,
my Google-foo is poor today and I can't find any discussion about
"inclusion of Codership's Galera patch to standard code-s
Hi, Honza!
On Feb 11, Honza Horak wrote:
> Hi guys,
>
> my Google-foo is poor today and I can't find any discussion about
> "inclusion of Codership's Galera patch to standard code-source of
> MariaDB". I'd like to see that one could just use the wresp plugin and
> have a working Galera cluster
Hi, I'll add $.02 more to this discussion.
Galera does not use the MySQL Pluggable Storage Engine Aarchitecture
(PSEA), because Galera needs, as pointed out by Justin, more
interaction with other storage engines (InnoDB currently, TokuDB in
future) and MySQL server, than what is provided by
Hi,
As I understand it, Galera doesn't work through the pluggable storage
engine API, so adding it via the engine interface is not an option. It
intercepts the binary log capture process, implements a global transaction
identifier and wire transaction state prototocol (wsrep), and is tightly
inte
Hi guys,
my Google-foo is poor today and I can't find any discussion about
"inclusion of Codership's Galera patch to standard code-source of
MariaDB". I'd like to see that one could just use the wresp plugin and
have a working Galera cluster (even if that would mean to introduce new
engine) w
6 matches
Mail list logo
