This is the main PostgreSQL git repository. http://git.postgresql.org/cgit/postgresql.git/atom?h=master 2026-01-14T14:12:25Z 2026-01-14T14:12:25Z Peter Eisentraut 2026-01-14T14:12:25Z urn:sha1:fa16e7fd84886643f480c36614fa11d45fc6d26f This reverts commit f0f2c0c1aef95757c4e7f144d5577e2b0d814279. The original problem that led to the use of pg_restrict was that MSVC couldn't handle plain restrict, and defining it to something else would conflict with its __declspec(restrict) that is used in system header files. In C11 mode, this is no longer a problem, as MSVC handles plain restrict. This led to the commit to replace pg_restrict with restrict. But this did not take C++ into account. Standard C++ does not have restrict, so we defined it as something else (for example, MSVC supports __restrict). But this then again conflicts with __declspec(restrict) in system header files. So we have to revert this attempt. The comments are updated to clarify that the reason for this is now C++ only. Reported-by: Jelte Fennema-Nio <postgres@jeltef.nl> Reviewed-by: Andres Freund <andres@anarazel.de> Discussion: https://www.postgresql.org/message-id/CAGECzQRoD7chJP1-dneSrhxUJv%2BBRcigoGOO4UwGzaShLot2Yw%40mail.gmail.com 2026-01-01T18:24:10Z Bruce Momjian 2026-01-01T18:24:10Z urn:sha1:451c43974f8e199097d97624a4952ad0973cea61 Backpatch-through: 14 2025-10-29T06:52:58Z Peter Eisentraut 2025-10-29T06:36:46Z urn:sha1:f0f2c0c1aef95757c4e7f144d5577e2b0d814279 MSVC in C11 mode supports the standard restrict qualifier, so we don't need the workaround naming pg_restrict anymore. Even though restrict is in C99 and should be supported by all supported compilers, we keep the configure test and the hardcoded redirection to __restrict, because that will also work in C++ in all supported compilers. (restrict is not part of the C++ standard.) For backward compatibility for extensions, we keep a #define of pg_restrict around, but our own code doesn't use it anymore. Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://www.postgresql.org/message-id/flat/0e3d8644-c01d-4374-86ea-9f0a987981f0%40eisentraut.org 2025-01-01T16:21:55Z Bruce Momjian 2025-01-01T16:21:55Z urn:sha1:50e6eb731d98ab6d0e625a0b87fb327b172bbebd Backpatch-through: 13 2024-11-06T10:11:52Z Peter Eisentraut 2024-11-06T10:06:58Z urn:sha1:ecb5af779877ad3f84e60112ecf0b138e97b847c as determined by IWYU Similar to commit dbbca2cf299, but for bin and some related files. Discussion: https://www.postgresql.org/message-id/flat/0df1d5b1-8ca8-4f84-93be-121081bde049%40eisentraut.org 2024-01-04T01:49:05Z Bruce Momjian 2024-01-04T01:49:05Z urn:sha1:29275b1d177096597675b5c6e7e7c9db2df8f4df Reported-by: Michael Paquier Discussion: https://postgr.es/m/ZZKTDPxBBMt3C0J9@paquier.xyz Backpatch-through: 12 2023-01-02T20:00:37Z Bruce Momjian 2023-01-02T20:00:37Z urn:sha1:c8e1ba736b2b9e8c98d37a5b77c4ed31baf94147 Backpatch-through: 11 2022-09-13T14:10:44Z Peter Eisentraut 2022-09-13T14:10:44Z urn:sha1:45b1a67a0fcb3f1588df596431871de4c93cb76f Rather than replace each unprintable byte with a '?' character, replace it with a hex escape instead. The API now allocates a copy rather than modifying the input in place. Author: Jacob Champion <jchampion@timescale.com> Discussion: https://www.postgresql.org/message-id/CAAWbhmgsvHrH9wLU2kYc3pOi1KSenHSLAHBbCVmmddW6-mc_=w@mail.gmail.com 2022-01-08T00:04:57Z Bruce Momjian 2022-01-08T00:04:57Z urn:sha1:27b77ecf9f4d5be211900eda54d8155ada50d696 Backpatch-through: 10 2021-01-02T18:06:25Z Bruce Momjian 2021-01-02T18:06:25Z urn:sha1:ca3b37487be333a1d241dab1bbdd17a211a88f43 Backpatch-through: 9.5