On Tue, 28 Feb 2023 at 09:25, Faustin Lammler wrote:
>
> Hi Matteo!
> I am not in charge of doing uploads to Debian FTP so, I don't know.
>
> @Otto do you know when 10.5.19 will be uploaded?
Only Debian release team knows the exact date. Page
https://release.debian.org/ says mid-February.
You
Hi Matteo!
I am not in charge of doing uploads to Debian FTP so, I don't know.
@Otto do you know when 10.5.19 will be uploaded?
Regards,
--
Faustin
GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79
signature.asc
Description: PGP signature
Hi Faustin,
mariadb 10.5.19 was released 3 weeks ago.
Is there a timeline for the release or the corresponding Debian package in
bullseye?
Thanks
MAtteo
If you received this email in error, please notify the sender and read our
confidentiality and data protection disclaimer:
Hi all, there is an upstream release 10.5.19 with hopefully a fix:
https://mariadb.com/kb/en/mariadb-10-5-19-release-notes/
On Thu, 12 Jan 2023 08:55:06 + Matteo Valsasna
wrote:
> Thanks a lot Faustin
>
>
>
> I found an useful description of MDEV-29988 in a comment to one of its
Thanks a lot Faustin
I found an useful description of MDEV-29988 in a comment to one of its
duplicates, and it matches quite well our application scenario for the database
connection that cause the memory leak according to
information_schema.PROCESSLIST.memory_used
(prepared statements
Hi!
Xan Charbonnet ,
10/01/2023 – 10:07:02 (-0600):
> It looks to me like https://jira.mariadb.org/browse/MDEV-29988 is very
> likely to be the issue we're seeing. Fortunately (if I'm interpreting
> upstream's JIRA correctly), it looks like a fix exists and will be included
> in 10.5.19.
Faustin,
Thanks for looking into this, and for your work packaging MariaDB for
Debian.
It looks to me like https://jira.mariadb.org/browse/MDEV-29988 is very
likely to be the issue we're seeing. Fortunately (if I'm interpreting
upstream's JIRA correctly), it looks like a fix exists and
Hi,
first of all, thank you all for the excellent (and detailed) report!
I don't see anything that could be related with Debian packaging of
MariaDB and so I suggest you check directly upstream.
I have searched into https://jira.mariadb.org and the closest report
that I can come with is
Dear Mantainer,
We are experiencing a similar memory leak after porting an application from
Debian 9 (mariadb 10.1.41-MariaDB-0+deb9u1) to Debian 11
(10.5.18-MariaDB-0+deb11u1)
1. the mariadb memory footprint (/proc/pid/status:VmSize) at mariadb startup
is 3GB, with
Package: mariadb-server-10.5
Version: 1:10.5.18-0+deb11u1
Severity: important
Dear Maintainer,
I run a pair of nameservers, and after a recent round of minor software
updates (see below for the complete list), mariadbd was OOM'd on both
machines.
These machines are minimal VMs: one has 512MB
10 matches
Mail list logo
