Re: POC: make mxidoff 64 bits

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: POC: make mxidoff 64 bits
Date: 2026-01-05 04:34:45
Message-ID: C41F944C-E2BB-4562-BCA3-FB678CE475D6@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Jan 5, 2026, at 02:06, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>
> Yes, you're right. Good catch! Committed the fix, thanks.
>
> - Heikki

Hi Heikki,

I actually reviewed this patch and had a comment on slur_io.c, but I don’t know why I left my comment email in the draft box and never sent it out.

The comment was that:
```
+void
+FreeSlruRead(SlruSegState *state)
+{
+ Assert(!state->writing); /* read only mode */
+
+ if (state->fd != -1)
+ close(state->fd);
+ pg_free(state);
+}

+void
+FreeSlruWrite(SlruSegState *state)
+{
+ Assert(state->writing);
+
+ SlruFlush(state);
+
+ if (state->fd != -1)
+ close(state->fd);
+ pg_free(state);
+}
```

In both FreeSlruRead() and FreeSlruWrite(), as we pg_free(state), I don’t see a reason why we don’t free state->dir and state->fn as well, because they are allocated by pstrdup and psrintf, which looks like memory leaks.

I made a change as the attached diff. Please see if you agree with the change.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

Attachment Content-Type Size
slru_io_memory.diff application/octet-stream 1.1 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Prafulla Ranadive 2026-01-05 05:28:00 Need help with postgresql build on windows
Previous Message Henson Choi 2026-01-05 04:29:44 Re: SQL Property Graph Queries (SQL/PGQ)