Postgres error upgrading from 3.3 to 3.4 caused by locale issues

Falco · January 2, 2025, 1:00am

Maybe related to your change @featheredtoast ?

github.com/discourse/discourse_docker

DEV: generate only en_us locales

discourse:main ← discourse:generate-locales

opened 06:53PM - 31 Aug 24 UTC

featheredtoast

+9 -5

Wondering if we really need all locales installed in the base image here. Ins…talling the pre-built locales-all package via apt takes 245MB Generating just c and en_us locales takes 22MB @xfalcox I know it's been a while since the move to debian, but do you remember if this is necessary? One guess I have is the original call to locale-gen was being called a few layers later, with no locale.gen configuration file -- I'm assuming locale-gen en_US used to work, but it doesn't appear to actually do anything in debian given debian's default `/etc/locale.gen` is empty

Topic		Replies	Views
Upgrade Failed from 2.7.0.beta1 to 2.7.0.beta3 Installation	13	1866	February 15, 2021
PostgreSQL Stuck During Rebuilding Installation	52	659	October 4, 2024
Failed upgrade from 2.5.0beta4 to 2.5.0beta5 Installation	6	1009	June 29, 2020
Urgent, rebuild failed from old version Installation	5	403	May 8, 2023
Upgrade from 2.8.0.beta10 to 3.1.0.beta1 failed on Ubuntu 16.04 Installation	3	640	January 26, 2023

Postgres error upgrading from 3.3 to 3.4 caused by locale issues

Related topics