Re: initdb's -c option behaves wrong way?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>,
Robert Haas <robertmhaas@gmail.com>,
Alvaro Herrera <alvherre@alvh.no-ip.org>,
pgsql-hackers@lists.postgresql.org
Date: 2024-03-04T01:01:36Z
Lists: pgsql-hackers
Attachments
- v5-0001-Make-initdb-c-option-case-insensitive.patch (text/x-diff) patch v5-0001
Daniel Gustafsson <daniel@yesql.se> writes: > I took the liberty to add this to the upcoming CF to make sure we don't lose > track of it. Thanks for doing that, because the cfbot pointed out a problem: I should have written pg_strncasecmp not strncasecmp. If this version tests cleanly, I'll push it. regards, tom lane
Commits
-
Fix initdb's -c option to treat the GUC name case-insensitively.
- fce2ce797c41 17.0 landed
- b78f4d22b2f2 16.3 landed