Skip to content

Commit f818551

Browse files
Handle alphanumeric characters in matching GUC names
The check for whether all GUCs are present in the sample config file used the POSIX character class :alpha: which corresponds to alphabet and not alphanumeric. Since GUC names can contain digits as well we need to use the :alnum: character class instead. Author: Daniel Gustafsson <daniel@yesql.se> Discussion: https://postgr.es/m/2CB04559-B1D8-4558-B6F0-8F09093D629F@yesql.se
1 parent e546989 commit f818551

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/test/modules/test_misc/t/003_check_guc.pl

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@
5656
# file.
5757
# - Valid configuration options are followed immediately by " = ",
5858
# with one space before and after the equal sign.
59-
if ($line =~ m/^#?([_[:alpha:]]+) = .*/)
59+
if ($line =~ m/^#?([_[:alnum:]]+) = .*/)
6060
{
6161
# Lower-case conversion matters for some of the GUCs.
6262
my $param_name = lc($1);

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy