postgresql.git/src/tools/check_bison_recursion.pl, branch masterThis is the main PostgreSQL git repository.http://git.postgresql.org/cgit/postgresql.git/atom?h=master2026-01-01T18:24:10ZUpdate copyright for 20262026-01-01T18:24:10ZBruce Momjian2026-01-01T18:24:10Zurn:sha1:451c43974f8e199097d97624a4952ad0973cea61
Backpatch-through: 14
Update copyright for 20252025-01-01T16:21:55ZBruce Momjian2025-01-01T16:21:55Zurn:sha1:50e6eb731d98ab6d0e625a0b87fb327b172bbebd
Backpatch-through: 13
Update copyright for 20242024-01-04T01:49:05ZBruce Momjian2024-01-04T01:49:05Zurn:sha1:29275b1d177096597675b5c6e7e7c9db2df8f4df
Reported-by: Michael Paquier
Discussion: https://postgr.es/m/ZZKTDPxBBMt3C0J9@paquier.xyz
Backpatch-through: 12
Make all Perl warnings fatal2023-12-29T17:20:00ZPeter Eisentraut2023-12-29T17:01:53Zurn:sha1:c5385929593dd8499cfb5d85ac322e8ee1819fd4
There are a lot of Perl scripts in the tree, mostly code generation
and TAP tests. Occasionally, these scripts produce warnings. These
are probably always mistakes on the developer side (true positives).
Typical examples are warnings from genbki.pl or related when you make
a mess in the catalog files during development, or warnings from tests
when they massage a config file that looks different on different
hosts, or mistakes during merges (e.g., duplicate subroutine
definitions), or just mistakes that weren't noticed because there is a
lot of output in a verbose build.
This changes all warnings into fatal errors, by replacing
use warnings;
by
use warnings FATAL => 'all';
in all Perl files.
Discussion: https://www.postgresql.org/message-id/flat/06f899fd-1826-05ab-42d6-adeb1fd5e200%40eisentraut.org
Pre-beta mechanical code beautification.2023-05-19T21:24:48ZTom Lane2023-05-19T21:24:48Zurn:sha1:0245f8db36f375326c2bae0c3420d3c77714e72d
Run pgindent, pgperltidy, and reformat-dat-files.
This set of diffs is a bit larger than typical. We've updated to
pg_bsd_indent 2.1.2, which properly indents variable declarations that
have multi-line initialization expressions (the continuation lines are
now indented one tab stop). We've also updated to perltidy version
20230309 and changed some of its settings, which reduces its desire to
add whitespace to lines to make assignments etc. line up. Going
forward, that should make for fewer random-seeming changes to existing
code.
Discussion: https://postgr.es/m/20230428092545.qfb3y5wcu4cm75ur@alvherre.pgsql
Update copyright for 20232023-01-02T20:00:37ZBruce Momjian2023-01-02T20:00:37Zurn:sha1:c8e1ba736b2b9e8c98d37a5b77c4ed31baf94147
Backpatch-through: 11
Update copyright for 20222022-01-08T00:04:57ZBruce Momjian2022-01-08T00:04:57Zurn:sha1:27b77ecf9f4d5be211900eda54d8155ada50d696
Backpatch-through: 10
Update copyright for 20212021-01-02T18:06:25ZBruce Momjian2021-01-02T18:06:25Zurn:sha1:ca3b37487be333a1d241dab1bbdd17a211a88f43
Backpatch-through: 9.5
Update copyrights for 20202020-01-01T17:21:45ZBruce Momjian2020-01-01T17:21:45Zurn:sha1:7559d8ebfa11d98728e816f6b655582ce41150f3
Backpatch-through: update all files in master, backpatch legal files through 9.4
Update copyright for 20192019-01-02T17:44:25ZBruce Momjian2019-01-02T17:44:25Zurn:sha1:97c39498e5ca9208d3de5a443a2282923619bf91
Backpatch-through: certain files through 9.4