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 spectacularily Support	25	376	February 10, 2025
Upgrade Failed from 2.7.0.beta1 to 2.7.0.beta3 Installation	13	1873	February 15, 2021
Hundreds of megabytes of apparently duplicate locale .js files Support	7	75	April 3, 2025
Database files are incompatible with server (updating inside Linode) Support	14	156	February 6, 2025
PostgreSQL Stuck During Rebuilding Installation	52	770	October 4, 2024

Postgres error upgrading from 3.3 to 3.4 caused by locale issues

Related topics