aboutsummaryrefslogtreecommitdiff
path: root/databases/mysqlwsrep57-server/files/patch-storage_myisam_mi__dynrec.c
diff options
context:
space:
mode:
Diffstat (limited to 'databases/mysqlwsrep57-server/files/patch-storage_myisam_mi__dynrec.c')
-rw-r--r--databases/mysqlwsrep57-server/files/patch-storage_myisam_mi__dynrec.c23
1 files changed, 23 insertions, 0 deletions
diff --git a/databases/mysqlwsrep57-server/files/patch-storage_myisam_mi__dynrec.c b/databases/mysqlwsrep57-server/files/patch-storage_myisam_mi__dynrec.c
new file mode 100644
index 000000000000..282cffdbcbc5
--- /dev/null
+++ b/databases/mysqlwsrep57-server/files/patch-storage_myisam_mi__dynrec.c
@@ -0,0 +1,23 @@
+--- storage/myisam/mi_dynrec.c.orig 2016-03-28 18:06:12 UTC
++++ storage/myisam/mi_dynrec.c
+@@ -65,18 +65,13 @@ my_bool mi_dynmap_file(MI_INFO *info, my
+ DBUG_RETURN(1);
+ }
+ /*
+- I wonder if it is good to use MAP_NORESERVE. From the Linux man page:
+- MAP_NORESERVE
+- Do not reserve swap space for this mapping. When swap space is
+- reserved, one has the guarantee that it is possible to modify the
+- mapping. When swap space is not reserved one might get SIGSEGV
+- upon a write if no physical memory is available.
++ MAP_NORESERVE is unimplemented in FreeBSD
+ */
+ info->s->file_map= (uchar*)
+ my_mmap(0, (size_t) size,
+ info->s->mode==O_RDONLY ? PROT_READ :
+ PROT_READ | PROT_WRITE,
+- MAP_SHARED | MAP_NORESERVE,
++ MAP_SHARED,
+ info->dfile, 0L);
+ if (info->s->file_map == (uchar*) MAP_FAILED)
+ {