| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Stan Hu <stanhu(at)gmail(dot)com> |
| Subject: | Re: PostgreSQL does not compile on macOS SDK 15.0 |
| Date: | 2024-07-05 00:04:01 |
| Message-ID: | 106836.1720137841@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> I had been thinking that I should try harder to make the pg_ prefix
> compile-time configurable (imagine some kind of string-pasting macros
> constructing the names), so that TCL and PG could have fewer diffs.
> But we're already not doing that for the function names, so unless Tom
> wants me to try to do that...?
Nah, I don't see much point in that.
> It's a funny position to finish up in: we have pg_ functions, pg_
> types but still standard REG_XXX macros. In the future someone might
> want to rename them all to PG_REG_XXX, so that we completely move out
> of the way of the system regex stuff. But not today, and certainly
> not in back-branches.
That would be an API break for any extensions using our regex code,
so I'm not especially in favor of it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-07-05 00:35:19 | Re: Pluggable cumulative statistics |
| Previous Message | Thomas Munro | 2024-07-04 23:54:29 | Re: PostgreSQL does not compile on macOS SDK 15.0 |