Download Latest Version v3.4.0 source code.tar.gz (3.0 MB)
Email in envelope

Get an email when there's a new version of Memgraph

Home / v3.2.1
Name Modified Size InfoDownloads / Week
Parent folder
README.md 2025-05-09 2.3 kB
v3.2.1 source code.tar.gz 2025-05-09 2.8 MB
v3.2.1 source code.zip 2025-05-09 4.5 MB
Totals: 3 Items   7.4 MB 0

Memgraph v3.2.1 - May 9th, 2025

🛠️ Improvements

  • Modified the Docker image such that the memgraph user has the UID 101 to match that used by MAGE. If the user has any volumes mounted on older versions or memgraph (< 3.2.1), then they should chown 101:101 /path/to/volume to allow the memgraph user to read and write to them. #2947
  • New relwithdebinfo Docker build for arm64 to allow users to debug Memgraph on ARM. Push relwithdebinfo DEB packages and Docker images to download bucket during release, so they are available here #2952
  • Improved the performance when writing to disk log stores’ durable data using batched writing. Users can expect the same behavior as before, with a slightly better performance when using high availability. #2946

🐞 Bug fixes

  • Fixed PageSlabMemoryResource large allocation returning wrong address. Creating deltas with large properties would correctly allocate memory, but cause an out-of-bounds write. Users shouldn’t see segfaults on commits or GC runs anymore. #2950
  • Fixed CallProcedureCursor reset method. Query modules would sometimes cause a crash due to not being reset properly. #2953
  • Fixed impersonate user misalignment between interpreter and session. This broke the permissions when using the impersonated user. User can now actually use the feature and see the correct behavior. #2938
  • Fixed query type deduction giving the wrong answer in cases where subqueries execute read procedures. Without the fix users could not execute certain queries. Query type misalignment shouldn’t occur anymore. #2944
  • Improved usages of read-modify-write pattern in the Raft code by using compare exchange operations instead of blindly loading, modifying and then storing again. Users should expect the same behaviour from the perspective of correctness but with a smaller chance of something getting inconsistent. #2937
Source: README.md, updated 2025-05-09