diff options
| author | Dean Rasheed <dean.a.rasheed@gmail.com> | 2024-06-04 11:51:25 +0100 |
|---|---|---|
| committer | Dean Rasheed <dean.a.rasheed@gmail.com> | 2024-06-04 11:51:25 +0100 |
| commit | b4e909082fa114d5934ca622b225d2352ec639fa (patch) | |
| tree | 7869348297d305f4b0a955c8744e41f5c5961b03 /src/backend | |
| parent | 3a2cc5a5b99ab04b9dc7e5f6c46b564739b5eb1b (diff) | |
| download | postgresql-b4e909082fa114d5934ca622b225d2352ec639fa.tar.gz postgresql-b4e909082fa114d5934ca622b225d2352ec639fa.zip | |
Fix PL/pgSQL's handling of integer ranges containing underscores.
Commit faff8f8e47 allowed integer literals to contain underscores, but
failed to update the lexer's "numericfail" rule. As a result, a
decimal integer literal containing underscores would fail to parse, if
used in an integer range with no whitespace after the first number,
such as "1_001..1_003" in a PL/pgSQL FOR loop.
Fix and backpatch to v16, where support for underscores in integer
literals was added.
Report and patch by Erik Wienhold.
Discussion: https://postgr.es/m/808ce947-46ec-4628-85fa-3dd600b2c154%40ewie.name
Diffstat (limited to 'src/backend')
| -rw-r--r-- | src/backend/parser/scan.l | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/parser/scan.l b/src/backend/parser/scan.l index 07d6cef2e41..54c54f4313b 100644 --- a/src/backend/parser/scan.l +++ b/src/backend/parser/scan.l @@ -407,7 +407,7 @@ octfail 0[oO]_? binfail 0[bB]_? numeric (({decinteger}\.{decinteger}?)|(\.{decinteger})) -numericfail {decdigit}+\.\. +numericfail {decinteger}\.\. real ({decinteger}|{numeric})[Ee][-+]?{decinteger} realfail ({decinteger}|{numeric})[Ee][-+] |