On Wed, Oct 14, 2026 at 3:30 AM Tom Lane <[email protected]> wrote: > I think that restricting things like that would provide a reasonable > compromise between safety and losing translation altogether.
Matching all three encodings may not be sufficient, since, e.g., OUTPUT_CHARSET can also affect the locale encoding? I'm also not sure whether matching all three is sufficient on Windows. > where addQueryComment contains the logic to decide whether translation > is safe and then also adds the comment syntax. Agreed. If we cannot guarantee the translation's encoding, falling back to the original English label would preserve it in server logs and avoid stripping comments during execution. Regards, -- Fujii Masao
