On Sat, Dec 7, 2024 at 7:51 AM Tom Lane <t...@sss.pgh.pa.us> wrote: > Over in the discussion of bug #18735, I've come to the realization > that these problems apply equally to the filesystem path names that > the server deals with: not only the data directory path, but the > path to the installation files [1]. Can we apply the same sort of > restrictions to those? I'm envisioning that initdb would check > either encoding-validity or all-ASCII-ness of those path names > depending on which mode it's setting the server up in.
Rabbit hole engaged. I am working on a generalisation, renamed to just CLUSTER ENCODING, covering all text that is not in a database but might be visible though database glasses (and probably more). Looking into pathnames and GUCs now. More soon.
