| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: Giving the shared catalogues a defined encoding |
| Date: | 2024-12-08 22:09:17 |
| Message-ID: | CA+hUKGL6ur9egBW-E9dm=fuE8yVz355oQiWU2nZTCK1D7-Draw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 7, 2024 at 7:51 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2024-12-08 23:12:32 | Re: Refactoring postmaster's code to cleanup after child exit |
| Previous Message | Jelte Fennema-Nio | 2024-12-08 22:08:47 | Re: Add a warning message when using unencrypted passwords |