andrei.el...@pp.inet.fi writes:
> Why won't we defer the current eager/optimistic old sub-id records
> discard in rpl_slave_state::record_gtid()
> mysql_mutex_lock(_slave_state);
> if ((elist= elem->grab_list()) != NULL)
> {
> /* Delete any old stuff, but keep around the most recent
Hello.
I can't help you with Jira because I do not know answers.
But I know you just can write some patch and submit it on github.
Guide is here https://mariadb.org/get-involved/getting-started-for-developers/
Feel free to ask any question in that mailing list.
11.10.2018, 17:42, "Takashi
Kristian, salute.
> Hi Andrei!
>
> Can you review this patch?
Thanks for taking care of this critical and complicated issue!
I studied the patch to have understand its idea of basically
implementing a roll-back to the slave gtid state as the slave
transaction participant resource.
This would be
Hello,
I wanted to contribute something to MariaDB, so I signed up to Jira,
but how can I assign an existing ticket to myself?
[programming experience]:
I have been programming for over 10 years but recently using Java,
Python, Node.js at work and C ++ is a little played a few years ago.
Hi Varun,
On Wed, Sep 12, 2018 at 06:13:23PM +0530, Varun wrote:
> revision-id: 1edec241473a122553fa9a27be995f3aef52654e
> (mariadb-10.3.7-171-g1edec241473)
> parent(s): 5a1868b58d26b286b6ad433096e7184895953311
> author: Varun Gupta
> committer: Varun Gupta
> timestamp: 2018-09-12 18:10:16 +0530
5 matches
Mail list logo
