- discuss - lists.mariadb.org

[Maria-discuss] Making wsrep_sst_mariabackup more SELinux friendly
by Scott A. Wozny 23 May '20

23 May '20

I’m switching over from Percona XtraDB Cluster 5.7 to MariaDB 10.3 with Galera support on CentOS 7. During this process things have gone mostly smoothly, but I’ve found a lot of SELinux AVC failures once I started testing. Some googling later and I found this article which describes the heart of my issue and it appears to center around a fix that was put into wsrep_sst_xtrabackup-v2 in the Percona repositories, but still exists in wsrep_sst_mariabackup (which, I guess, was ported AFTER Percona made their changes). https://dzone.com/articles/lock-down-enforcing-selinux-with-percona-xtradb-… For the TL;DR set, the crux is this. In the wsrep_sst_mariabackup script, the wait_for_listen function scans all the processes, which upsets SELinux who either forbids or logs the scan of every listening process on the system that mysqld_t doesn’t have rights to do a process getattr on. Solutions to this include runing SELinux in permission mode or allowing a process getattr from mysqld_t to every type attached to a listening process, neither of which is appealing. So where MariaDB 10.3 wsrep_sst_mariabackup calls wait_for_listen() like this: wait_for_listen ${SST_PORT} ${ADDR} ${MODULE} & and executes this function: # waits ~10 seconds for nc to open the port and then reports ready # (regardless of timeout) wait_for_listen() { local PORT=$1 local ADDR=$2 local MODULE=$3 for i in {1..50} do if [ "$OS" = "FreeBSD" ];then sockstat -46lp $PORT | grep -qE "^[^ ]* *(socat|nc) *[^ ]* *[^ ]* *[^ ]* *[^ ]*:$PORT" &&$ else ss -p state listening "( sport = :$PORT )" | grep -qE 'socat|nc' && break fi sleep 0.2 done echo "ready ${ADDR}/${MODULE}//$sst_ver" } Which causes SELinux to light up like a Christmas tree. PXC 5.7’s wsrep_sst_xtrabackup-v2 calls wait_for_listen() like this: # Note: this is started as a background process # So it has to wait for processes that are started by THIS process wait_for_listen $$ ${WSREP_SST_OPT_HOST} ${WSREP_SST_OPT_PORT:-4444} ${MODULE} & and executes this function: # waits ~1 minute for nc/socat to open the port and then reports ready # (regardless of timeout) # # Assumptions: # 1. The socat/nc processes do not launch subprocesses to handle # the connections. Note that socat can be configured to do so. # 2. socat is not bound to a specific interface/address, so the # IP portion of the local address is all zeros (0000...000). # # Parameter 1: the pid of the wsrep_sst_xtrabackup-v2 process. We are looking # for the socat process that was started by this script. # Parameter 2: the IP address of the SST host # Parameter 3: the Port of the SST host # Parameter 4: a descriptive name for what we are doing at this point # wait_for_listen() { local parentpid=$1 local host=$2 local port=$3 local module=$4 # # Check to see if the OS supports /proc/<pid>/net/tcp # if [[ ! -r /proc/$$/net/tcp && ! -r /proc/$$/net/tcp6 ]]; then wsrep_log_debug "$LINENO: Using ss for socat/nc discovery" # Revert to using ss to check if socat/nc is listening wsrep_check_program ss if [[ $? -ne 0 ]]; then wsrep_log_error "******** FATAL ERROR *********************** " wsrep_log_error "* Could not find 'ss'. Check that it is installed and in the path." wsrep_log_error "******************************************** " return 2 fi for i in {1..300} do ss -p state listening "( sport = :${port} )" | grep -qE 'socat|nc' && break sleep 0.2 done echo "ready ${host}:${port}/${module}//$sst_ver" return 0 fi wsrep_log_debug "$LINENO: Using /proc/pid/net/tcp for socat/nc discovery" # Get the index for the 'local_address' column in /proc/xxxx/net/tcp # We expect this to be the same for IPv4 (net/tcp) and IPv6 (net/tcp6) local ip_index=0 local header if [[ -r /proc/$$/net/tcp ]]; then read -ra header <<< $(head -n 1 /proc/$$/net/tcp) elif [[ -r /proc/$$/net/tcp6 ]]; then read -ra header <<< $(head -n 1 /proc/$$/net/tcp6) else wsrep_log_error "******** FATAL ERROR *********************** " wsrep_log_error "* Cannot find /proc/$$/net/tcp (or tcp6)" wsrep_log_error "******************************************** " exit 1 fi for i in "${!header[@]}"; do if [[ ${header[$i]} = "local_address" ]]; then # Add one to the index since arrays are 0-based # but awk is 1-based ip_index=$(( i + 1 )) break fi done if [[ $ip_index -eq 0 ]]; then wsrep_log_error "******** FATAL ERROR *********************** " wsrep_log_error "* Unexpected /proc/xx/net/tcp layout: cannot find local_address" wsrep_log_error "******************************************** " exit 1 fi wsrep_log_debug "$LINENO: local_address index is $ip_index" local port_in_hex port_in_hex=$(printf "%04X" $port) local user_id user_id=$(id -u) for i in {1..300} do # List all socat/nc processes started by the user of this script # Then look for processes that have the script pid as a parent prcoess # somewhere in the process tree wsrep_log_debug "$LINENO: Entering loop body : $i" # List only socat/nc processes started by this user to avoid triggering SELinux for pid in $(ps -u $user_id -o pid,comm | grep -E 'socat|nc' | awk '{ printf $1 " " }') do if [[ -z $pid || $pid = " " ]]; then continue fi wsrep_log_debug "$LINENO: Examining pid: $pid" # Now get the processtree for this pid # If the parentpid is NOT in the process tree, then ignore if ! echo "$(get_parent_pids $pid)" | grep -qw "$parentpid"; then wsrep_log_debug "$LINENO: $parentpid is not in the process tree: $(get_parent_pids $pid)" continue fi # get the sockets for the pid # Note: may not need to get the list of sockets, is it ok to # just look at the list of local addresses in tcp? local sockets sockets=$(ls -l /proc/$pid/fd | grep socket | cut -d'[' -f2 | cut -d ']' -f1 | tr '\n' '|') # remove the trailing '|' sockets=${sockets%|} wsrep_log_debug "$LINENO: sockets: $sockets" if [[ -n $sockets ]]; then # For the network addresses, we expect to be listening # on all interfaces, thus the address should be # 00..000:PORT (all zeros for the IP address). # Dumping the data in the lines #if [[ -n "$WSREP_LOG_DEBUG" ]]; then # lines=$(grep -E "\s(${sockets})\s" /proc/$pid/net/tcp) # if [[ -n $lines ]]; then # while read -r line; do # if [[ -z $line ]]; then # continue # fi # wsrep_log_debug "$LINENO: $line" # done <<< "$lines\n" # fi #fi # Checking IPv4 if grep -E "\s(${sockets})\s" /proc/$pid/net/tcp | awk "{print \$${ip_index}}" | grep -q "^00*:${port_in_hex}$"; then wsrep_log_debug "$LINENO: found a match for pid: $pid" break 2 fi # Also check IPv6 if grep -E "\s(${sockets})\s" /proc/$pid/net/tcp6 | awk "{print \$${ip_index}}" | grep -q "^00*:${port_in_hex}$"; then break 2 fi fi done sleep 0.2 done wsrep_log_debug "$LINENO: wait_for_listen() exiting" echo "ready ${host}:${port}/${module}//$sst_ver" return 0 } which does NOT light up SELinux like a Christmas tree (but DOES still require a few SELinux policy additions to run in enforcing mode). Obviously the PXC function code isn’t directly compatible with the Mariabackup sst script since at the very least it’s not using the same parameters, but can I just change the calling line AND the function itself in my version of wsrep_sst_mariabackup and will it work, or is it more complicated than that? There are also other SELinux AVC failures that I’m prepared to write custom policy for, but I’d like to “patch” the wait_for_listen function in wsrep_sst_mariabackup so I don’t have to remember every time I add a listening daemon on the server that I need to rebuild my custom SELinux policy. If the author of the article is correct, the custom SELinux policy allows needed OUTSIDE the noisy listening port scan should be pretty static and only need a re-check on major version upgrades. So, I know this was a lot and if you think I should take this to the devs list, please let me know. I was hoping there might be a powerful enough user on this list who could suggest the code changes needed in wsrep_sst_mariabackup to get me around the most onerous part of this, OR whatever changes I might need to make outside of drag-and-drop. Thanks, Scott

1 1

[Maria-discuss] migrate gtid replica to cluster member
by Jeff Dyke 22 May '20

22 May '20

I asked here a while ago in here about my inability to make physical mariabackups viable in a new server, it would eventually fail a restart ( i had a test that failed that led me to look into this). This was in one AWS environment(VPC). In the end there were no disk problems, no corrupt tables, no read issues with aria or innodbcheck as well as an online check with mysqlcheck. And as i said in the earlier email, it works perfect in staging. Some of you may remember that. Anyway, to my satisfaction, i have solved that problem, and its more scorched earth solution than anything, happy to elaborate after. No I have two very stable slaves set in strict gtid mode and I want to add them to the cluster that i am having an issue with, eventually retiring old nodes. I have brought up new cluster nodes on so many occasions, but never transitioned from a replica and i don't trust the output of the current cluster SSTs, but it may work now, with my new setups. I'll test that and ask this at the same time. I can layout a base plan for what i would do, but i'm asking for folks that have had to deal with this to compare my notes with. - All servers in the same VPC, spread across AZs, all IAM roles/policies fully in place. - These are mariadb/galera nodes, not members of an RDS cluster. I had needs that RDS didn't have when i built out this layout, in case you're curious or want to say move to RDS. Thanks if you have pointers. This is all mariadb 10.4.12/13. If i can tie this one up, i can release a bunch of simple set of bash scripts but make it safe to run on clusters, regardless if you're testing or provisioning, even as a pipiline test. Thanks again,

1 0

[Maria-discuss] Connector/C Types and Definitions vs Data Types in MariaDB
by Jogchum Reitsma 18 May '20

18 May '20

Hi, As a little learning project I want to program a test case to insert some rows in a table, using MariaDB Connector/C API Prepared Statement . <https://mariadb.com/kb/en/mariadb-connectorc-api-prepared-statement-functio…> That table has column definitions adhering to the MariaDB Data Types, as described in https://mariadb.com/kb/en/data-types/ Following the example given in https://mariadb.com/kb/en/bulk-insert-row-wise-binding/, I want to set the buffer and buffer_type values of the MSQL_BIND struct. But I'm somewhat at a loss here, because the before mentioned datatypes described in https://mariadb.com/kb/en/data-types/ do not always match with the Connector/C Types and Definitions given in https://mariadb.com/kb/en/connectorc-types-and-definitions/ For example, the latter has MYSQL_TYPE_INT24, which is not present in the former. Field types are defined in mariadb_com.h, but the size and the value ranges are not given there, nor at https://mariadb.com/kb/en/connectorc-types-and-definitions/ Hence, especially for the types present in only the list in Connector/C Types and Definitions, I don't know their size and value, and how to connect them to he gcc types. Anyone here who can guide me on this? cheers, Jogchum

1 0

Re: [Maria-discuss] Mariadb 10.3 crashing continuously on Centos 8
by Ralf Hartings 18 May '20

18 May '20

Hi again, Here are the more detailed files and info regarding your questions. The attachments contain the non-truncated output from the systemctl and the journalctl commands. The attachment 2020-05-08..... contains the content of the my.cnf files. It looks like no special options were given here, all is pretty standard - as I never changed anything in these files. db At least not as I am aware of, since I installed mariadb last year and no problems sinces yesterday... Further to your question on the repo, I am using the CENTOS8 packages, version 10.3 : > > [root@server1 Documents]# rpm -qa | grep maria > mariadb-server-utils-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > mariadb-backup-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > mariadb-connector-c-3.0.7-1.el8.x86_64 > mariadb-gssapi-server-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > mariadb-connector-c-config-3.0.7-1.el8.noarch > mariadb-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > mariadb-errmsg-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > mariadb-server-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > mariadb-common-10.3.17-1.module_el8.1.0+257+48736ea6.x86_64 > [root@server1 Documents]# > Regarding ulimit, to my knowledge, I have never changed anything here since I installed mariadb.... The only thing I can find on this is the executable at /usr/bin/ulimit As said, my biggest question and concern is: how could this suddenly happen yesterday, without me doing any changes/updates in the server in the last 2 weeks? I am very grateful for any comments/hints to solve this. Could a forced re-installl of the above packages help to put everything back to"standard"? /Ralf On Sunday 17/05/2020 at 16:15, Gordan Bobic wrote: > > There are several obvious issues in what you posted, to so > with ulimit. You need to look at your service scripts and make > sure that they set suitable limits for what you are > configuring in my.cnf. > Are you using the CentOS 8 bundled MariaDB 10.3 or the > packages from the MariaDB repositories? > > Your journalctl output seems incomplete. systemctl status > output may also be useful (make sure neither is truncated in > width). > > Comment out all of your tuning options and see if it > starts then. Unless you know _exactly_ what you are doing or > had somebody who _really_ knows what they are doing change > any options other than innodb_buffer_pool_size, you should > probably leave them at defaults. > > > > On Sun, May 17, 2020 at 3:00 PM Ralf Hartings > <ralf(a)hartings.se> wrote: > >> Hi >> >> My up-to-date Wordpress website running with mariadb 10.3 on >> CentOS8 (up >> to date) has been running for a long time without any >> issues. >> Suddenly, yesterday, my server became unreachable and did >> not respond to >> anything. Only power off/on helped to get it to respond >> again, but the >> website is down. >> I did not update the server in the last 2 weeks. No changes >> whatsoever. >> >> The logs show the mariadb server is restarting and crashing >> continuously. >> I switched off the mariadb.service to avoid any possible >> further issues, >> as I run a mailserver on the same machine (which runs just >> fine now). >> >> Please look at my post in the CentOS forum: >> https://forums.centos.org/viewtopic.php?f=54&t=74436&p=313469#p313469 >> The people there are great experts in CentOS, but probably >> no experts in >> mariadb in the same way as you are, and I really would like >> to get my >> site up again ASAP. >> >> Thanks a lot for reading this post and helping me out on >> this! >> >> /Ralf >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~maria-discuss >> Post to : maria-discuss(a)lists.launchpad.net >> Unsubscribe : https://launchpad.net/~maria-discuss >> More help : https://help.launchpad.net/ListHelp >> _______________________________________________ > Mailing list: https://launchpad.net/~maria-discuss > Post to : maria-discuss(a)lists.launchpad.net > Unsubscribe : https://launchpad.net/~maria-discuss > More help : https://help.launchpad.net/ListHelp > >

1 0

[Maria-discuss] Mariadb 10.3 crashing continuously on Centos 8
by Ralf Hartings 18 May '20

18 May '20

Hi My up-to-date Wordpress website running with mariadb 10.3 on CentOS8 (up to date) has been running for a long time without any issues. Suddenly, yesterday, my server became unreachable and did not respond to anything. Only power off/on helped to get it to respond again, but the website is down. I did not update the server in the last 2 weeks. No changes whatsoever. The logs show the mariadb server is restarting and crashing continuously. I switched off the mariadb.service to avoid any possible further issues, as I run a mailserver on the same machine (which runs just fine now). Please look at my post in the CentOS forum: https://forums.centos.org/viewtopic.php?f=54&t=74436&p=313469#p313469 The people there are great experts in CentOS, but probably no experts in mariadb in the same way as you are, and I really would like to get my site up again ASAP. Thanks a lot for reading this post and helping me out on this! /Ralf

3 3

Re: [Maria-discuss] Nosql language with plugins
by Justin Swanhart 16 May '20

16 May '20

I am not going to engage with you on this mailing list. On Thu, May 14, 2020, 1:44 PM Reindl Harald <h.reindl(a)thelounge.net> wrote: > just a dumb fucker which don't realize that his idiot posts talking to > himslef are annoying and if he once again comes with "You want a flame war? > I was a Usenet admin. I know the game. I will burn you to the ground and > piss on your ashes" and take the challenge and make this idot my new hobby > Am 14.05.20 um 19:38 schrieb Jan Steinman: > > "Closed: Fixed None Opened 5 years ago by rhughes.” > > FIVE YEARS AGO! > > Grudge much? > > On May 14, 2020, at 10:30, Justin Swanhart <greenlion(a)gmail.com> wrote: > > https://pagure.io/CoC/issue/6 > > On Thu, May 14, 2020, 1:28 PM Reindl Harald <h.reindl(a)thelounge.net> > wrote: > >> > I had to go on disability for mental health reasons >> >> didn't work well - shut the fuck up! >> >> Am 14.05.20 um 19:20 schrieb Justin Swanhart: >> > I propose we just let it go. >> > >> > I will never speak of MariaDB again and you stop fucking me over. We >> > both win. >> > >> > Can we please just stop this stupid fight. I have nothing to gain by >> > tilting and windmills and you have nothing to gain by doing demonstrably >> > shitty things to me. >> > >> > On Mon, May 11, 2020, 5:57 PM Justin Swanhart <greenlion(a)gmail.com >> > <mailto:greenlion@gmail.com>> wrote: >> > >> > MariaDB isn't an honest actor. They repeatedly utilize FUD to push >> > their agenda. >> > >> > I was so frustrated by the columnstore experience that I had to go >> > on disability for mental health reasons, and I was fired while on >> > disability for blogging about BSL. >> > >> > To attack me for my religious views after criticizing their >> > characterization of RedShift on LinkedIn was unconscionable. The >> > account had zero connections, no activity except commenting on my >> > post, had only one job listed (33 years it said) and the university >> > the person claimed to be from did not have the person in the alumni >> > directory. >> > >> > MariaDB won't respond to this, but you know it is true because there >> > was no reason other than spite to remove articles about my tools >> > that I did not even contribute and which are now dead links from >> > other community webpages and blogs. >> > >> > On Mon, May 11, 2020, 5:41 PM Justin Swanhart <greenlion(a)gmail.com >> > <mailto:greenlion@gmail.com>> wrote: >> > >> > >> > ---------- Forwarded message --------- >> > From: *Justin Swanhart* <greenlion(a)gmail.com >> > <mailto:greenlion@gmail.com>> >> > Date: Mon, May 11, 2020, 5:38 PM >> > Subject: Re: [Maria-discuss] Nosql language with plugins >> > To: Roberto Spadim <roberto(a)spadim.com.br >> > <mailto:roberto@spadim.com.br>> >> > >> > >> > MariaDB relicensed MaxScale from GPL to Business Source >> > License. The license change effectively extorted customers >> > requiring customers using it to pay for it. While older >> > versions of MaxScale become GPL, the license terms prohibit >> > backporting any security fixes and MariaDB abandons each release >> > and never backports any fixes so it is impossible to use old >> > versions in production. >> > >> > On Mon, May 11, 2020, 5:34 PM Roberto Spadim >> > <roberto(a)spadim.com.br <mailto:roberto@spadim.com.br>> wrote: >> > >> > What’s BSL? >> > >> > Em seg, 11 de mai de 2020 às 18:19, Justin Swanhart >> > <greenlion(a)gmail.com <mailto:greenlion@gmail.com>> >> escreveu: >> > >> > *crickets* >> > >> > On Fri, May 8, 2020, 2:33 PM Justin Swanhart >> > <greenlion(a)gmail.com <mailto:greenlion@gmail.com>> >> wrote: >> > >> > Seems I didn't get Federico's reply. The answer is >> > because: >> > War, war never changes... >> > >> > I made a stink about BSL, and I have shamed Monty in >> > public. >> > >> > MariaDB recently created a sock puppet LinkedIn >> > account to attack me for my religious views. >> > >> > We are at war >> > >> > On Wed, Apr 29, 2020, 9:48 PM Justin Swanhart >> > <greenlion(a)gmail.com <mailto:greenlion@gmail.com>> >> > wrote: >> > >> > MariaDB doesn't have rewrite plugins. >> > >> > What you want could still not be done with a >> > preparse plugin in MySQL because there is no way >> > to speak an arbitrary protocol. You could have >> > a client that speaks the MySQL protocol but >> > sends non-sql text commands that have some 1:1 >> > match with SQL, for example MDX. >> > >> > For MySQL 8 I have developed an alternative >> > rewrite plugin interface that can execute any >> > number of SQL statements serially on the THD of >> > the client connection, or an arbitrary THD. It >> > would be possible to port to MariaDB but as >> > MariaDB has deleted the KB entries related to my >> > tools, I highly doubt they would upstream it, >> > and I would expect some form of >> > compensation/sponsorship from you if you wanted >> > me to do it. In any case the plugin would still >> > not speak arbitrary binary protocols. >> > >> > MySQL 8 supports the X protocol for document >> > access. It would probably be possible to create >> > an X protocol proxy that speaks arbitrary >> > protocols but that would be a big project that >> > probably not many people would be interested >> in. >> > >> > On Wed, Apr 29, 2020, 9:14 PM Roberto Spadim >> > <roberto(a)spadim.com.br >> > <mailto:roberto@spadim.com.br>> wrote: >> > >> > Could be possible use the query rewrite >> > plugin to execute no sql commands? Something >> > like disable sql parser and execute some >> > specific protocol, returning standard sql >> > datasets as result? > > >

4 4

[Maria-discuss] Fwd: Nosql language with plugins
by Justin Swanhart 14 May '20

14 May '20

---------- Forwarded message --------- From: Justin Swanhart <greenlion(a)gmail.com> Date: Mon, May 11, 2020, 5:38 PM Subject: Re: [Maria-discuss] Nosql language with plugins To: Roberto Spadim <roberto(a)spadim.com.br> MariaDB relicensed MaxScale from GPL to Business Source License. The license change effectively extorted customers requiring customers using it to pay for it. While older versions of MaxScale become GPL, the license terms prohibit backporting any security fixes and MariaDB abandons each release and never backports any fixes so it is impossible to use old versions in production. On Mon, May 11, 2020, 5:34 PM Roberto Spadim <roberto(a)spadim.com.br> wrote: > What’s BSL? > > Em seg, 11 de mai de 2020 às 18:19, Justin Swanhart <greenlion(a)gmail.com> > escreveu: > >> *crickets* >> >> On Fri, May 8, 2020, 2:33 PM Justin Swanhart <greenlion(a)gmail.com> wrote: >> >>> Seems I didn't get Federico's reply. The answer is because: >>> War, war never changes... >>> >>> I made a stink about BSL, and I have shamed Monty in public. >>> >>> MariaDB recently created a sock puppet LinkedIn account to attack me for >>> my religious views. >>> >>> We are at war >>> >>> On Wed, Apr 29, 2020, 9:48 PM Justin Swanhart <greenlion(a)gmail.com> >>> wrote: >>> >>>> MariaDB doesn't have rewrite plugins. >>>> >>>> What you want could still not be done with a preparse plugin in MySQL >>>> because there is no way to speak an arbitrary protocol. You could have a >>>> client that speaks the MySQL protocol but sends non-sql text commands that >>>> have some 1:1 match with SQL, for example MDX. >>>> >>>> For MySQL 8 I have developed an alternative rewrite plugin interface >>>> that can execute any number of SQL statements serially on the THD of the >>>> client connection, or an arbitrary THD. It would be possible to port to >>>> MariaDB but as MariaDB has deleted the KB entries related to my tools, I >>>> highly doubt they would upstream it, and I would expect some form of >>>> compensation/sponsorship from you if you wanted me to do it. In any case >>>> the plugin would still not speak arbitrary binary protocols. >>>> >>>> MySQL 8 supports the X protocol for document access. It would probably >>>> be possible to create an X protocol proxy that speaks arbitrary protocols >>>> but that would be a big project that probably not many people would be >>>> interested in. >>>> >>>> On Wed, Apr 29, 2020, 9:14 PM Roberto Spadim <roberto(a)spadim.com.br> >>>> wrote: >>>> >>>>> Could be possible use the query rewrite plugin to execute no sql >>>>> commands? Something like disable sql parser and execute some specific >>>>> protocol, returning standard sql datasets as result? >>>>> -- >>>>> Roberto Spadim >>>>> SPAEmpresarial - Software ERP/Scada >>>>> Eng. Automação e Controle, Eng. Financeira >>>>> _______________________________________________ >>>>> Mailing list: https://launchpad.net/~maria-discuss >>>>> Post to : maria-discuss(a)lists.launchpad.net >>>>> Unsubscribe : https://launchpad.net/~maria-discuss >>>>> More help : https://help.launchpad.net/ListHelp >>>>> >>>> -- > Roberto Spadim > SPAEmpresarial - Software ERP/Scada > Eng. Automação e Controle, Eng. Financeira >

2 6

[Maria-discuss] Is galera 26.4.4 a pre-rc version?
by Adam Purkrt 13 May '20

13 May '20

Hi, I do not understand the following: MariaDB has been shipping galera 26.4.x line for some time now - for example, with yesterday's release of 10.4.13, which is Stable (GA), there is galera 26.4.4 for download https://downloads.mariadb.org/mariadb/10.4.13/ How come that on https://galeracluster.com/downloads/ which is the origin of galera (afaict) the currently most advanced version in the 4.x line is only release candidate? the version is 4.5 (i.e. 26.4.5) and it is RC it seems like the whole galera 26.4.x line up to now (26.4.1, 26.4.2, 26.4.3. 26.4.4) are only pre-release versions(?) Or do I get it wrong? Thanks Adam Purkrt

2 1

[Maria-discuss] is galera 26.4.4 a pre-rc version?
by Adam Purkrt 13 May '20

13 May '20

Hi, I do not understand the following: MariaDB has been shipping galera 26.4.x line for some time now - for example, with yesterday's release of 10.4.13, which is Stable (GA), there is galera 26.4.4 for download https://downloads.mariadb.org/mariadb/10.4.13/ How come that on https://galeracluster.com/downloads/ which is the origin of galera (afaict) the currently most advanced version in the 4.x line is only RC? 4.5.rc (i.e. 26.4.5.rc) to be exact there are no publicly available 4.x (i.e. 26.4.x) downloads so it seems like the whole galera 26.4.x line up to now (26.4.1, 26.4.2, 26.4.3. 26.4.4) are only pre-release versions(?) Or do I get it wrong? Thanks Adam Purkrt

1 0

[Maria-discuss] Nosql language with plugins
by Roberto Spadim 11 May '20

11 May '20

Could be possible use the query rewrite plugin to execute no sql commands? Something like disable sql parser and execute some specific protocol, returning standard sql datasets as result? -- Roberto Spadim SPAEmpresarial - Software ERP/Scada Eng. Automação e Controle, Eng. Financeira

3 4