| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: retire MemoryContextResetAndDeleteChildren backwards compatibility macro |
| Date: | 2023-11-14 16:20:16 |
| Message-ID: | 202311141620.5utqdkrxibkh@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-Nov-13, Nathan Bossart wrote:
> Shall we retire this backwards compatibility macro at this point? A search
> of https://codesearch.debian.net/ does reveal a few external uses, so we
> could alternatively leave it around and just update Postgres to stop using
> it, but I don't think it would be too burdensome for extension authors to
> fix if we removed it completely.
Let's leave the macro around and just remove its uses in PGDG-owned
code. Having the macro around hurts nothing, and we can remove it in 15
years or so.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Entristecido, Wutra (canción de Las Barreras)
echa a Freyr a rodar
y a nosotros al mar"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2023-11-14 16:33:39 | Re: retire MemoryContextResetAndDeleteChildren backwards compatibility macro |
| Previous Message | Peter Eisentraut | 2023-11-14 16:15:49 | Re: Why do indexes and sorts use the database collation? |