This is the main PostgreSQL git repository. http://git.postgresql.org/cgit/postgresql.git/atom?h=master 2026-01-01T18:24:10Z 2026-01-01T18:24:10Z Bruce Momjian 2026-01-01T18:24:10Z urn:sha1:451c43974f8e199097d97624a4952ad0973cea61 Backpatch-through: 14 2025-01-01T16:21:55Z Bruce Momjian 2025-01-01T16:21:55Z urn:sha1:50e6eb731d98ab6d0e625a0b87fb327b172bbebd Backpatch-through: 13 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-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 2020-01-01T17:21:45Z Bruce Momjian 2020-01-01T17:21:45Z urn:sha1:7559d8ebfa11d98728e816f6b655582ce41150f3 Backpatch-through: update all files in master, backpatch legal files through 9.4 2019-01-02T17:44:25Z Bruce Momjian 2019-01-02T17:44:25Z urn:sha1:97c39498e5ca9208d3de5a443a2282923619bf91 Backpatch-through: certain files through 9.4 2018-01-03T04:30:12Z Bruce Momjian 2018-01-03T04:30:12Z urn:sha1:9d4649ca49416111aee2c84b7e4441a0b7aa2fac Backpatch-through: certain files through 9.3 2017-07-30T23:18:21Z Andres Freund 2017-07-17T07:33:49Z urn:sha1:cc9f08b6b813e30789100b6b34110d8be1090ba0 This allows us to add stack-depth checks the first time an executor node is called, and skip that overhead on following calls. Additionally it yields a nice speedup. While it'd probably have been a good idea to have that check all along, it has become more important after the new expression evaluation framework in b8d7f053c5c2bf2a7e - there's no stack depth check in common paths anymore now. We previously relied on ExecEvalExpr() being executed somewhere. We should move towards that model for further routines, but as this is required for v10, it seems better to only do the necessary (which already is quite large). Author: Andres Freund, Tom Lane Reported-By: Julien Rouhaud Discussion: https://postgr.es/m/22833.1490390175@sss.pgh.pa.us https://postgr.es/m/b0af9eaa-130c-60d0-9e4e-7a135b1e0c76@dalibo.com