From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Noah Misch <noah(at)leadboat(dot)com> |
Cc: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Euler Taveira <euler(at)eulerto(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Small memory fixes for pg_createsubcriber |
Date: | 2025-04-01 23:22:47 |
Message-ID: | 75977C31-35E5-4158-A4C1-A6488DC496C3@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Apr 2, 2025, at 5:14, Noah Misch <noah(at)leadboat(dot)com> wrote:
Yes, pg_upgrade should not do that. I was trying to explain the difference
between NULL and 'NULL'. I didn't mean pg_upgrade should emit "IS NULL".
(Apologies for the probably-weirdly-formatted message)
This issue has been already mentioned around here, with patches exchanged:
Re: pgsql: pg_upgrade: Fix inconsistency in memory freeing
postgresql.org
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Junwang Zhao | 2025-04-01 23:25:12 | Re: general purpose array_sort |
Previous Message | Peter Geoghegan | 2025-04-01 23:02:54 | Re: Adding skip scan (including MDAM style range skip scan) to nbtree |