| From: | Asim R P <apraveen(at)pivotal(dot)io> |
|---|---|
| To: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Shared buffer access rule violations? |
| Date: | 2018-08-08 01:43:57 |
| Message-ID: | CANXE4Tfxmjv8Z-kcwWUCYxx6zCFS=GeBPm-ZjjLucvrGewjUtg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Facility-to-detect-shared-buffer-access-violations.patch | text/x-patch | 11.4 KB |
| 0002-Fix-known-but-not-problematic-buffer-access-violatio.patch | text/x-patch | 1.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2018-08-08 02:00:27 | Re: Shared buffer access rule violations? |
| Previous Message | Tom Lane | 2018-08-07 23:09:49 | Re: Internal error XX000 with enable_partition_pruning=on, pg 11 beta1 on Debian |