Re: Shared buffer access rule violations?
P <apraveen@pivotal.io>
From: Asim R P <apraveen@pivotal.io>
To: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2018-08-08T01:43:57Z
Lists: pgsql-hackers
Attachments
- 0001-Facility-to-detect-shared-buffer-access-violations.patch (text/x-patch) patch 0001
- 0002-Fix-known-but-not-problematic-buffer-access-violatio.patch (text/x-patch) patch 0002
Please find attached a patch to mark a shared buffer as read-write or read-only using mprotect(). The idea is to catch violations of shared buffer access rules. This patch was useful to detect the access violations reported in this thread. The mprotect() calls are enabled by -DMPROTECT_BUFFER compile time flag. Asim
Commits
-
Fix inadequate buffer locking in FSM and VM page re-initialization.
- 0cf3363c0110 9.3.24 landed
- 6d2d5ab173a9 9.4.19 landed
- 17c3dabbb70c 9.5.14 landed
- 073ffefd8082 9.6.10 landed
- f1963a1e79a4 10.5 landed
- 5586e42b3493 11.0 landed
- 130beba36d6d 12.0 landed