Download raw body.
Update: PostgreSQL 16.4 -- initdb fails for me
Hi, On Wednesday, August 28, 2024 12:23 CEST, "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> wrote: > Hi, > > On Thursday, August 08, 2024 16:40 CEST, Jeremy Evans <jeremy@openbsd.org> wrote: > > > This updates PostgreSQL to the latest release. Release announcement at: > > https://www.postgresql.org/about/news/postgresql-164-158-1413-1316-1220-and-17-beta-3-released-2910/ > > > > Fixes CVE-2024-7348: PostgreSQL relation replacement during pg_dump > > executes arbitrary SQL > > > > Tested briefly on amd64. I'll be doing some additional testing, and > > will be committing in a couple days unless I hear objections. > > > > As this fixes a CVE, I will be backporting this to -stable. > > > > Thanks, > > Jeremy > > I just tried to re-create one of my systems, which apparently runs postgres. > don't know which version was the last before, where it "just worked", but it's the same way I usually run it > via Puppet: > > It fails for me to: > > /usr/local/bin/initdb --pgdata '/var/postgresql/data' > The files belonging to this database system will be owned by user "_postgresql". > This user must also own the server process. > > The database cluster will be initialized with locale "en_US.UTF-8". > The default database encoding has accordingly been set to "UTF8". > The default text search configuration will be set to "english". > > Data page checksums are disabled. > > fixing permissions on existing directory /var/postgresql/data ... ok > creating subdirectories ... ok > selecting dynamic shared memory implementation ... posix > selecting default max_connections ... 100 > selecting default shared_buffers ... 128MB > selecting default time zone ... Europe/Berlin > creating configuration files ... ok > running bootstrap script ... ok > performing post-bootstrap initialization ... 2024-08-28 09:53:04.861 CEST [60355] FATAL: text search configuration "french" does not exist > 2024-08-28 09:53:04.861 CEST [60355] STATEMENT: ALTER TEXT SEARCH CONFIGURATION french ADD MAPPING > FOR word, hword_part, hword > WITH french_stem; > /* > * text search configuration for german language > * > * Copyright (c) 2007-2023, PostgreSQL Global Development Group > * > * src/backend/snowball/snowball.sql.in > * > * german and certain other macros are replaced for each language; > * see the Makefile for details. > * > * Note: this file is read in single-user -j mode, which means that the > * command terminator is semicolon-newline-newline; whenever the backend > * sees that, it stops and executes what it's got. If you write a lot of > * statements without empty lines between, they'll all get quoted to you > * in any error message about one of them, so don't do that. Also, you > * cannot write a semicolon immediately followed by an empty line in a > * string literal (including a function body!) or a multiline comment. > */ > > CREATE TEXT SEARCH DICTIONARY german_stem > (TEMPLATE = snowball, Language = german , StopWords=german); > > child process exited with exit code 1 > initdb: removing contents of data directory "/var/postgresql/data" on some other host I have a happily running 16.2. Haven't yet spotted the difference. Sebastian
Update: PostgreSQL 16.4 -- initdb fails for me