mariadb version > 10.1 changed the default row_format
from COMPACT to DYNAMIC. system upgraded to 7.5 therefore
end up with table partitions with different row_format, since
creating tables do not honour row_format (mysql bug 95478).
this in turn causes "ALTER TABLE .. EXCHANGE PARTITION .."
statements to fail with an error 1731 ("non matching attribute
ROW_FORMAT between table and partition", see MDEV-26027).
a manual mitigation would mean to align the row_formats
using "ALTER TABLE .. ROW_FORMAT = ..". But this in turn can
result fail with erro 1118 ("row size too large") for tables
with many&long columns (ie. accounting.cdr).
this fix will now mitigate the situation by falling back to
the built-in rowcopy method, if it detects mismatching
row_format.
Change-Id: Ief220be41b2350fa1437b6f35d46d1811facb57f
(cherry picked from commit 12de9892f8)
* cleanup_data():
- print error message when deletion from a table
fails (usually a non-exiting table is provided)
- amount of affected rows is set to 0 if undefined
Change-Id: I066041aae5d6a65c766480a2bbaf976c6563d188
(cherry picked from commit 1a86ba1286)
Rename it to match the current naming convention, and add backwards
compatibility symlinks until the next LTS.
Change-Id: I0c02c8695fc37f8e7a7e15114c0b7a7f7545d102
* if a use-partitioning is enabled for a table
and this table is not suitable for it, the table
is processed using the sql backup method.
Change-Id: Ia3d8bc4701cc31fed54465227e49ec4563e5c100
Modern ngcp-service knows when and how to handle monit interactions if
needed. Switch to the new interface, so that we can then easily remove
monit from NGCP.
Change-Id: Ie1a4e3cd44255888dd016c1a37cf3038de832a63
This makes it obvious these are NGCP specific programs, and avoids
possible collisions with other third party programs.
Create backward compatibility symlinks for a smoother transition.
Change-Id: Id7ca1e517ae4da46f5e25534d334f1f3352d1b87
mr5.5 has migrated from ngcp-sems 1.4 to sems-pbx 2.x and the folder
/var/spool/ngcp/moh/ was no longer in use, moreover it is not created
on newly installed servers since mr5.5
It is time to clean it to prevent missunderstandings here.
Change-Id: I75cdeba9c3652fe8944f3c1321cceb27c22e5fa6
* backup-months is replaced by keep-months
* backup-retro is removed, now everything that is
below keep-months is backed up
* backup-months and backup-retro are marked as deprecated
and acc-cleanup stops with the a mandatory request to
upgrade the config file
* "over-a-year" months difference is now correctly calculated
* slightly simplified min-max dates calculations and iterations
Change-Id: If1e4ae95713a06dc140a4c1f322d23e496493dda