Re: Remove PG_MMAP_FLAGS

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: Remove PG_MMAP_FLAGS
Date: 2026-01-23 10:03:33
Message-ID: CAExHW5uN1T2LRf7WypNT8ZyJ0yY_pp4Zo4uNH7m_Pxr1AuW0nQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 23, 2026 at 10:12 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Fri, Jan 23, 2026 at 08:04:18AM +0530, Ashutosh Bapat wrote:
> > As Peter mentioned in the shared buffers resizing thread [1] it's
> > placement and name in mem.h led us to think that it affects all mmap
> > calls or that all mmap calls should use those flags. Neither of which
> > is true. We have different mmap calls using different set of flags.
> > Attached patch proposes changes similar (not exact) as you suggest
> > above. Please take a look.
> >
> > [1] https://www.postgresql.org/message-id/12add41a-7625-4639-a394-a5563e349322@eisentraut.org
>
> Okay, point taken. I can live with your patch suggestion based on
> what you have attached.

Thanks.

I revised the patch a bit. The macro had parenthesis around the macro
definition which are not required in the assignment. Removed them.
Also revised the commit message a bit.

--
Best Wishes,
Ashutosh Bapat

Attachment Content-Type Size
v20260123_2-0001-Remove-PG_MMAP_FLAGS.patch text/x-patch 2.8 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zsolt Parragi 2026-01-23 10:07:03 Re: docs: clarify ALTER TABLE behavior on partitioned tables
Previous Message Jim Jones 2026-01-23 09:57:48 Re: ALTER TABLE: warn when actions do not recurse to partitions