네, 경고는 새로 생긴 것들입니다(수정이 필요합니다). 하지만 이 경고는 초기 파일을 시스템으로 복사하는 명령어에만 영향을 미치며, 업데이트와는 무관합니다. 가장 유력한 추측은 데이터베이스가 LANG가 적용되기 전에 초기화되었기 때문에 데이터베이스 업데이트 시에만 문제가 발생한다는 것입니다.
해결 방법으로, 업그레이드할 때 LANG을 일시적으로 en_US.UTF-8으로 설정하고, 완료 후 원래 값으로 되돌리는 것을 시도해 볼 수 있습니다. (물론 백업을 반드시 받아두세요)
저에게는 실패했고, 로케일(locale) 관련 문제도 있었던 것 같습니다.
$ cat postgres_data_new/pg_upgrade_output.d/20250131T032317.601/log/pg_upgrade_server.log
-----------------------------------------------------------------
pg_upgrade run on Fri Jan 31 03:23:17 2025
-----------------------------------------------------------------
command: "/usr/lib/postgresql/13/bin/pg_ctl" -w -l "/var/lib/postgresql/15/data/pg_upgrade_output.d/20250131T032317.601/log/pg_upgrade_server.log" -D "/var/lib/postgresql/13/data" -o "-p 50432 -b -c listen_addresses='' -c unix_socket_permissions=0700 -c unix_socket_directories='/var/lib/postgresql'" start >> "/var/lib/postgresql/15/data/pg_upgrade_output.d/20250131T032317.601/log/pg_upgrade_server.log" 2>&1
waiting for server to start....2025-01-31 03:23:17.761 UTC [268] LOG: invalid value for parameter "lc_messages": "ru_RU.UTF-8"
2025-01-31 03:23:17.761 UTC [268] LOG: invalid value for parameter "lc_monetary": "ru_RU.UTF-8"
2025-01-31 03:23:17.761 UTC [268] LOG: invalid value for parameter "lc_numeric": "ru_RU.UTF-8"
2025-01-31 03:23:17.761 UTC [268] LOG: invalid value for parameter "lc_time": "ru_RU.UTF-8"
2025-01-31 03:23:17.761 UTC [268] FATAL: configuration file "/var/lib/postgresql/13/data/postgresql.conf" contains errors
stopped waiting
pg_ctl: could not start server
Examine the log output.
app.yml 파일에 다음 내용을 설정하고 다시 빌드해 볼 수 있나요?
env:
LANG: 'ru_RU.UTF-8'
...
현재 확인되고 있는 오류는 Postgres error upgrading from 3.3 to 3.4 caused by locale issues 와 관련이 있을 가능성이 높습니다.
yml 파일에 설정되어 있습니다. 명확하지 않다면 죄송합니다. 수동 업데이트를 시도하고 있으며, tianon/postgres-upgrade:13-to-15 컨테이너를 단계별로 실행하고 해당 스크립트에 주석을 달았습니다.
컨테이너에서 ru_RU.UTF-8 로케일을 활성화하여 그 오류는 수정했지만, 이제 다른 오류가 발생했습니다:
Performing Consistency Checks
-----------------------------
Checking cluster versions ok
Checking database user is the install user ok
Checking database connection settings ok
Checking for prepared transactions ok
Checking for system-defined composite types in user tables ok
Checking for reg* data types in user tables ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking for user-defined encoding conversions ok
Checking for user-defined postfix operators ok
Checking for incompatible polymorphic functions ok
Creating dump of global objects ok
Creating dump of database schemas ok
lc_collate values for database "template1" do not match: old "ru_RU.UTF-8", new "en_US.utf8"
Failure, exiting
tianon 컨테이너에서 로케일을 업데이트한 후 postgres_data_new 디렉터리도 다시 생성하셨는지 확인해 주실 수 있을까요? 이전 실행에서 잘못된 로케일로 초기화되었을 가능성이 있으며, 이는 new "en_US.utf8"이라는 후속 오류를 보신 이유를 설명할 수 있습니다.
아직 이 작업을 수행하지 않으셨다면, docker-upgrade (이것은 새 데이터베이스 버전에 대한 initdb도 실행합니다.)을 실행하기 전에 tianon 컨테이너에서 적절한 로케일 설정을 구성해야 할 수도 있습니다. 가장 쉬운 방법은 app 컨테이너에서 로케일 관련 환경 변수를 복사하는 것입니다.
네, 그것이 문제의 일부였습니다! 감사합니다!
결국 두 가지 수정이 필요했습니다. 첫째는 이 댓글에 기반하여 POSTGRES_INITDB_ARGS="--locale=ru_RU.UTF-8"로 initdb 로케일을 설정하는 것이었고, 둘째는 로케일을 활성화하고 locale-gen을 실행하는 것이었습니다. 제 경우 스크립트는 다음과 같았습니다:
docker run --rm \
--entrypoint=/bin/bash \
-v /var/discourse/shared/standalone/postgres_data:/var/lib/postgresql/13/data \
-v /var/discourse/shared/standalone/postgres_data_new:/var/lib/postgresql/15/data \
-e POSTGRES_INITDB_ARGS="--locale=ru_RU.UTF-8" \
tianon/postgres-upgrade:13-to-15 \
-c "apt-get update && apt-get install -y postgresql-15-pgvector && sed -i 's/^# *\(ru_RU.UTF-8 UTF-8\)/\1/' /etc/locale.gen && locale-gen && docker-upgrade"
재빌드 시 소켓 문제가 발생하지 않도록 postgres_data 폴더의 권한도 수정해야 했습니다:
2025-01-31 05:38:30.430 GMT [44] LOG: skipping missing configuration file "/shared/postgres_data/postgresql.auto.conf"
2025-01-31 05:38:30.433 UTC [44] FATAL: data directory "/shared/postgres_data" has wrong ownership
2025-01-31 05:38:30.433 UTC [44] HINT: The server must be started by the user that owns the data directory.
I, [2025-01-31T05:38:35.384305 #1] INFO -- :
I, [2025-01-31T05:38:35.384481 #1] INFO -- : > /usr/local/bin/create_db
createdb: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory
Is the server running locally and accepting connections on that socket?
소유자가 누구여야 하는지 정확히 알지 못하고 기억도 나지 않아, 근처에 있던 postgres_backup과 postgres_run 폴더와 동일한 UID/GID를 지정했습니다.
chown -R 101:104 /var/discourse/shared/standalone/postgres_data
이제 모든 것이 정상 작동합니다!
피드백 주셔서 감사합니다. 불편을 드려 죄송합니다. 
아, 맞습니다. tianon 컨테이너는 postgres 사용자에게 다른 UID를 사용합니다.
권장 사항에 따라 OP의 지침을 업데이트했습니다. 감사합니다!
좋습니다, 한번 시도해 보겠습니다. 이는 app.yml의 아래 설정을 변경하라는 뜻인가요? 아니면 다른 작업(예: 호스트 시스템의 세션 설정 조정)이 필요한가요?
env:
LC_ALL: de_DE.UTF-8
LANG: de_DE.UTF-8
LANGUAGE: de_DE.UTF-8
화제에서 벗어난 질문일 수 있지만, LC_ALL을 사용 중이므로 LANG과 LANGUAGE가 정말 필요한가요?
하지만 네, 거기서는 로케일(locales)을 사용하고 있습니다.
정말 세심하게 배려해 주셨네요. 표준 클리업 스크립트에 이를 포함해 주셔서 감사합니다!
맞아요, 아마도 필요하지 않을 것 같습니다. 처음에 Discourse를 설치한 동료에게 왜 세 가지를 모두 삽입했는지 확인해봐야겠습니다.
저도 로케일(locales) 오류가 발생하고 있습니다.
(<unknown>): did not find expected key while parsing a block mapping at line 133 column 5 -e LANG=en_US.UTF-8
YAML syntax error. Please check your containers/*.yml config files.
원인은 yml 파일 하단의 간격 오류였습니다. 간격 오류를 수정한 후 업그레이드가 정상적으로 실행되었습니다.
app.yml에서 로케일을 교체하니 몇 단계는 더 진행되었지만, 불행히도 크게 달라지지 않았습니다. 여전히 무언가 잘못되고 있으며 postgres 업데이트가 올바르게 적용되지 않는 것 같습니다:
root@Ubuntu-2204-jammy-amd64-base /var/discourse # ./launcher rebuild app
x86_64 아키텍처 감지됨.
launcher가 최신 상태인지 확인 중
Fetching origin
Launcher는 최신 상태입니다
기존 컨테이너 중지 중
+ /usr/bin/docker stop -t 600 app
app
2.0.20250129-0720: Pulling from discourse/base
Digest: sha256:01b8516e5504c0e9bc3707773015ff4407be03a89154194ff3b5b8699291bc26
Status: Image is up to date for discourse/base:2.0.20250129-0720
docker.io/discourse/base:2.0.20250129-0720
/usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups.rb
/usr/local/bin/pups --stdin
I, [2025-02-01T22:43:22.046506 #1] INFO -- : Reading from stdin
I, [2025-02-01T22:43:22.090615 #1] INFO -- : File > /etc/service/postgres/run chmod: +x chown:
I, [2025-02-01T22:43:22.095189 #1] INFO -- : File > /etc/service/postgres/log/run chmod: +x chown:
I, [2025-02-01T22:43:22.113260 #1] INFO -- : File > /etc/runit/3.d/99-postgres chmod: +x chown:
I, [2025-02-01T22:43:22.116842 #1] INFO -- : File > /root/install_postgres chmod: +x chown:
I, [2025-02-01T22:43:22.120381 #1] INFO -- : File > /root/upgrade_postgres chmod: +x chown:
I, [2025-02-01T22:43:22.165502 #1] INFO -- : Replacing data_directory = '/var/lib/postgresql/15/main' with data_directory = '/shared/postgres_data' in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-01T22:43:22.192991 #1] INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-01T22:43:22.193261 #1] INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-01T22:43:22.193606 #1] INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-01T22:43:22.193923 #1] INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-01T22:43:22.194221 #1] INFO -- : Replacing (?-mix:#?default_text_search_config *=.*) with default_text_search_config = '$db_default_text_search_config' in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-01T22:43:22.194511 #1] INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-01T22:43:22.194789 #1] INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-01T22:43:22.242968 #1] INFO -- : Replacing (?-mix:#?log_min_duration_statement *=.*) with log_min_duration_statement = $db_log_min_duration_statement in /etc/postgresql/15/main/postgresql.conf
I, [2025-02-01T22:43:22.256930 #1] INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres peer in /etc/postgresql/15/main/pg_hba.conf
I, [2025-02-01T22:43:22.257319 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*127.*$) with host all all 0.0.0.0/0 md5 in /etc/postgresql/15/main/pg_hba.conf
I, [2025-02-01T22:43:22.257663 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*::1\/128.*$) with host all all ::/0 md5 in /etc/postgresql/15/main/pg_hba.conf
I, [2025-02-01T22:43:22.258234 #1] INFO -- : > if [ -f /root/install_postgres ]; then
/root/install_postgres && rm -f /root/install_postgres
elif [ -e /shared/postgres_run/.s.PGSQL.5432 ]; then
socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1
fi
2025/02/01 22:43:23 socat[33] E connect(, AF=1 "/shared/postgres_run/.s.PGSQL.5432", 36): Connection refused
I, [2025-02-01T22:43:23.856313 #1] INFO -- : Generating locales (this might take a while)...
en_US.UTF-8... done
Generation complete.
I, [2025-02-01T22:43:23.856538 #1] INFO -- : > HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/15/bin/postmaster -D /etc/postgresql/15/main
I, [2025-02-01T22:43:23.865162 #1] INFO -- : File > /usr/local/bin/create_db chmod: +x chown:
I, [2025-02-01T22:43:23.909221 #1] INFO -- : File > /var/lib/postgresql/take-database-backup chmod: +x chown: postgres:postgres
I, [2025-02-01T22:43:23.913112 #1] INFO -- : File > /var/spool/cron/crontabs/postgres chmod: chown:
I, [2025-02-01T22:43:23.913287 #1] INFO -- : > sleep 5
2025-02-01 22:43:25.004 UTC [35] FATAL: database files are incompatible with server
2025-02-01 22:43:25.004 UTC [35] DETAIL: The data directory was initialized by PostgreSQL version 13, which is not compatible with this version 15.10 (Debian 15.10-1.pgdg120+1).
저도 같은 오류가 발생했는데, 지금도 계속 실패하고 있습니다.
다음과 같이 시도해 보았습니다.
./discourse-doctor를 실행해 보았지만 실패했습니다.netstats 결과 해당 포트를 사용하는 프로세스가 없었습니다. 이후 인스턴스를 재시작하여 처음부터 다시 시작하고 앱을 다시 빌드해 보았지만, 여전히 실패합니다.
I, [2025-02-02T00:20:43.491510 #1] INFO -- : > if [ -f /root/install_postgres ]; then
/root/install_postgres && rm -f /root/install_postgres
elif [ -e /shared/postgres_run/.s.PGSQL.5432 ]; then
socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1
fi
2025/02/02 00:20:46 socat[33] E connect(, AF=1 "/shared/postgres_run/.s.PGSQL.5432", 36): Connection refused
I, [2025-02-02T00:20:46.466110 #1] INFO -- : Generating locales (this might take a while)...
en_US.UTF-8... done
Generation complete.
I, [2025-02-02T00:20:46.467179 #1] INFO -- : > HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/15/bin/postmaster -D /etc/postgresql/15/main
I, [2025-02-02T00:20:46.480451 #1] INFO -- : File > /usr/local/bin/create_db chmod: +x chown:
I, [2025-02-02T00:20:46.497621 #1] INFO -- : File > /var/lib/postgresql/take-database-backup chmod: +x chown: postgres:postgres
I, [2025-02-02T00:20:46.504526 #1] INFO -- : File > /var/spool/cron/crontabs/postgres chmod: chown:
I, [2025-02-02T00:20:46.505484 #1] INFO -- : > sleep 5
2025-02-02 00:20:46.647 UTC [35] FATAL: database files are incompatible with server
2025-02-02 00:20:46.647 UTC [35] DETAIL: The data directory was initialized by PostgreSQL version 13, which is not compatible with this version 15.10 (Debian 15.10-1.pgdg120+1).
I, [2025-02-02T00:20:51.511155 #1] INFO -- :
I, [2025-02-02T00:20:51.511342 #1] INFO -- : > /usr/local/bin/create_db
createdb: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
I, [2025-02-02T00:20:52.474702 #1] INFO -- :
I, [2025-02-02T00:20:52.475371 #1] INFO -- : > echo postgres installed!
I, [2025-02-02T00:20:52.478084 #1] INFO -- : postgres installed!
그리고
I, [2025-02-02T00:05:22.648865 #1] INFO -- : > sleep 5
2025-02-02 00:05:22.792 UTC [35] FATAL: database files are incompatible with server
2025-02-02 00:05:22.792 UTC [35] DETAIL: The data directory was initialized by PostgreSQL version 13, which is not compatible with this version 15.10 (Debian 15.10-1.pgdg120+1).
I, [2025-02-02T00:05:27.657230 #1] INFO -- :
I, [2025-02-02T00:05:27.657387 #1] INFO -- : > /usr/local/bin/create_db
481:M 02 Feb 2025 00:07:05.174 # Failed listening on port 6379 (TCP), aborting.
I, [2025-02-02T00:13:38.491603 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
URGENT: Failed to initialize site default: ActiveRecord::ConnectionNotEstablished connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused
Is the server running locally and accepting connections on that socket?
rake aborted!
ActiveRecord::ConnectionNotEstablished: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused (ActiveRecord::ConnectionNotEstablished)
Is the server running locally and accepting connections on that socket?
Caused by:
PG::ConnectionBad: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused (PG::ConnectionBad)
Is the server running locally and accepting connections on that socket?
나도 같은 문제인 것 같습니다.
방금 시도해 보니 제 서버에도 이 파일이 있고, 리빌드 실패가 발생하고 있습니다.
postgres@ubuntu-s-1vcpu-1gb-nyc3-01-app:/var/www/discourse$ ls -al /shared/postgres_run/.s.PGSQL.5432
srwxrwxrwx 1 postgres postgres 0 Feb 2 03:24 /shared/postgres_run/.s.PGSQL.5432
Hi @xFocus and @schneeland 
app 컨테이너를 중지할 때 데이터베이스가 정상적으로 종료되고 있나요? 로그는 OP의 출력과 비슷해야 합니다.
이 파일로 문제를 해결하려고 했지만 실패했습니다
mv /shared/postgres_run/.s.PGSQL.5432 /shared/postgres_run/.s.PGSQL.5432.2025Feb1BackUp
root@ubuntu-s-1vcpu-1gb-nyc3-01-app:/var/www/discourse# ls -al /shared/postgres_run/.s.PGSQL.5432*
srwxrwxrwx 1 postgres postgres 0 Feb 2 03:24 /shared/postgres_run/.s.PGSQL.5432.2025Feb1BackUp
-rw------- 1 postgres postgres 62 Feb 2 03:24 /shared/postgres_run/.s.PGSQL.5432.lock
그 후 재빌드도 여전히 실패하며, The source cluster was not shut down cleanly. 오류가 발생합니다.
@mwaniki
Stopping PostgreSQL 13 database server: main.
Stopping PostgreSQL 15 database server: main.
Performing Consistency Checks
-----------------------------
Checking cluster versions ok
The source cluster was not shut down cleanly.
Failure, exiting
-------------------------------------------------------------------------------------
UPGRADE OF POSTGRES FAILED
Please visit https://meta.discourse.org/t/postgresql-15-update/349515 for support.
You can run ./launcher start app to restart your app in the meanwhile
FAILED
--------------------
Pups::ExecError: if [ -f /root/install_postgres ]; then
/root/install_postgres && rm -f /root/install_postgres
elif [ -e /shared/postgres_run/.s.PGSQL.5432 ]; then
socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1
fi
failed with return #<Process::Status: pid 18 exit 1>
Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec failed with the params {"tag"=>"db", "cmd"=>"if [ -f /root/install_postgres ]; then\n /root/install_postgres && rm -f /root/install_postgres\nelif [ -e /shared/postgres_run/.s.PGSQL.5432 ]; then\n socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1\nfi\n"}
bootstrap failed with exit code 1
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
931142f4cf49942fb3faf0676818c6395376c9fb6c76008d82037b0b76ae7111
start와 stop을 다시 실행해 보았습니다
root@ubuntu-s-1vcpu-1gb-nyc3-01:/var/discourse# ./launcher start app
x86_64 arch detected.
starting up existing container
+ /usr/bin/docker start app
app
root@ubuntu-s-1vcpu-1gb-nyc3-01:/var/discourse# ./launcher stop app
x86_64 arch detected.
+ /usr/bin/docker stop -t 600 app
app
하지만 이 로그 파일이 없는데… 걱정해야 할까요?
Mwaniki님 감사합니다
root@ubuntu-s-1vcpu-1gb-nyc3-01:/var/discourse# tail -f shared/data/log/var-log/postgres/current
tail: cannot open 'shared/data/log/var-log/postgres/current' for reading: No such file or directory
tail: no files remaining
네, 오타였어요. 대신 shared/standalone/log/var-log/postgres/current을 확인해 주시겠어요? 방금 OP를 업데이트했어요.
맞아요, LOG: database system is shut down 로그를 보지 못했습니다.
아래는 ./launcher stop app 명령을 실행한 후 확인한 내용입니다. 그래서 재빌드(rebuild)를 진행할 때 해당 PostgreSQL 포트가 이미 사용 중이라는 오류가 발생한 것 같습니다.
2025-02-02 04:37:09.801 UTC [542] LOG: starting PostgreSQL 13.18 (Debian 13.18-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-02-02 04:37:09.804 UTC [542] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-02-02 04:37:09.806 UTC [542] LOG: listening on IPv6 address "::", port 5432
2025-02-02 04:37:09.820 UTC [542] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-02-02 04:37:09.851 UTC [562] LOG: database system was interrupted; last known up at 2025-02-02 04:31:58 UTC
2025-02-02 04:37:10.267 UTC [562] LOG: database system was not properly shut down; automatic recovery in progress
2025-02-02 04:37:10.278 UTC [562] LOG: redo starts at 2/DB0AFFE0
2025-02-02 04:37:10.280 UTC [562] LOG: invalid record length at 2/DB0B5958: wanted 24, got 0
2025-02-02 04:37:10.280 UTC [562] LOG: redo done at 2/DB0B3990
2025-02-02 04:37:10.349 UTC [542] LOG: database system is ready to accept connections
2025-02-02 04:38:08.161 UTC [1345] discourse@discourse LOG: duration: 101.966 ms bind <unnamed>: SELECT "posts"."id", "posts"."user_id", "posts"."topic_id", "posts"."post_number", "posts"."raw", "posts"."cooked", "posts"."created_at", "posts"."updated_at", "posts"."reply_to_post_number", "posts"."reply_count", "posts"."quote_count", "posts"."deleted_at", "posts"."off_topic_count", "posts"."like_count", "posts"."incoming_link_count", "posts"."bookmark_count", "posts"."score", "posts"."reads", "posts"."post_type", "posts"."sort_order", "posts"."last_editor_id", "posts"."hidden", "posts"."hidden_reason_id", "posts"."notify_moderators_count", "posts"."spam_count", "posts"."illegal_count", "posts"."inappropriate_count", "posts"."last_version_at", "posts"."user_deleted", "posts"."reply_to_user_id", "posts"."percent_rank", "posts"."notify_user_count", "posts"."like_score", "posts"."deleted_by_id", "posts"."edit_reason", "posts"."word_count", "posts"."version", "posts"."cook_method", "posts"."wiki", "posts"."baked_at", "posts"."baked_version", "posts"."hidden_at", "posts"."self_edits", "posts"."reply_quoted", "posts"."via_email", "posts"."raw_email", "posts"."public_version", "posts"."action_code", "posts"."locked_by_id", "posts"."image_upload_id", "posts"."outbound_message_id", "posts"."qa_vote_count" FROM "posts" WHERE "posts"."deleted_at" IS NULL ORDER BY "posts"."id" ASC LIMIT 1
2025-02-02 04:38:10.917 UTC [1341] discourse@discourse LOG: duration: 238.937 ms statement: WITH tags_included_cte AS (