Atualização do PostgreSQL 15

Anúncios
45

Sim, então os avisos são novos (e devem ser corrigidos), mas eles afetam apenas os comandos que copiam os arquivos iniciais para o sistema e não estão relacionados a atualizações. A melhor suspeita que temos é que o banco de dados foi inicializado antes que o LANG fosse aplicado, e isso causa problemas apenas com as atualizações do banco de dados.

Uma coisa a tentar é definir temporariamente o idioma para en_US.UTF-8 para a atualização e voltar depois. (obviamente, certifique-se de fazer backups)

2 curtidas
46

falhou para mim, algo com o locale também

$ 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.
2 curtidas
47

Você pode tentar definir o seguinte em seu arquivo app.yml e reconstruir?

env:
  LANG: 'ru_RU.UTF-8'
  ...

O erro que você está vendo provavelmente está relacionado a Postgres error upgrading from 3.3 to 3.4 caused by locale issues.

1 curtida
48

Eu tenho em yml, desculpe se não estiver claro, estou tentando o passo com o container tianon/postgres-upgrade:13-to-15 do manual de atualização e comentei nesse script.

Corrigi esse erro habilitando o locale ru_RU.UTF-8 no container, mas agora há outro:

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
1 curtida
49

Você poderia confirmar se também recriou o diretório postgres_data_new após atualizar o locale no contêiner tianon? Ele provavelmente foi iniciado com o locale incorreto nas execuções anteriores, o que pode explicar por que você viu o erro subsequente indicando new \"en_US.utf8\".

Se você ainda não fez isso, pode ser necessário definir as configurações de locale apropriadas no contêiner tianon antes de executar docker-upgrade (que também executa initdb para a nova versão do banco de dados). A maneira mais fácil seria copiar as variáveis de ambiente específicas do locale do seu contêiner app.

2 curtidas
50

Sim, essa foi parte do problema! Obrigado!

No final, precisei fazer duas modificações, a primeira é configurar o locale do initdb com POSTGRES_INITDB_ARGS=\"--locale=ru_RU.UTF-8\" (com base neste comentário), e a segunda é habilitar o locale e executar o locale-gen, então o script ficou assim para mim:

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"

Eu também precisei corrigir as permissões na pasta postgres_data, caso contrário, houve um problema de socket ao reconstruir:

2025-01-31 05:38:30.430 GMT [44] LOG:  pulando arquivo de configuração ausente "/shared/postgres_data/postgresql.auto.conf"
2025-01-31 05:38:30.433 UTC [44] FATAL:  o diretório de dados "/shared/postgres_data" tem propriedade incorreta
2025-01-31 05:38:30.433 UTC [44] HINT:  O servidor deve ser iniciado pelo usuário que possui o diretório de dados.
I, [2025-01-31T05:38:35.384305 #1]  INFO -- : 
I, [2025-01-31T05:38:35.384481 #1]  INFO -- : > /usr/local/bin/create_db
createdb: erro: a conexão com o servidor no socket "/var/run/postgresql/.s.PGSQL.5432" falhou: Nenhum arquivo ou diretório encontrado

	O servidor está em execução localmente e aceitando conexões nesse socket?

Não tenho certeza e não me lembro qual deveria ser o proprietário, então dei a ele o mesmo UID/GID das pastas postgres_backup e postgres_run que estavam próximas.

chown -R 101:104 /var/discourse/shared/standalone/postgres_data

Agora tudo funciona!

4 curtidas
51

Obrigado pelo feedback e desculpe pelos problemas. :slight_smile:

Ah, sim. O contêiner tianon usa um UID diferente para o usuário postgres.

Atualizei as instruções no OP com base nas suas recomendações. Obrigado!

1 curtida
52

Ok, posso tentar isso. Presumo que isso signifique alterar as configurações abaixo em app.yml? Ou há mais alguma coisa que preciso fazer? (por exemplo, ajustar as configurações de sessão no sistema host)

env:
  LC_ALL: de_DE.UTF-8
  LANG: de_DE.UTF-8
  LANGUAGE: de_DE.UTF-8
1 curtida
53

Isso pode estar fora do tópico, mas você realmente precisa de LANG e LANGUAGE, já que está usando LC_ALL?

Mas sim, é aí que você usa os locais.

1 curtida
54

Isso foi muito atencioso, que incluiu no script de limpeza padrão, obrigado!

1 curtida
55

Você está certo, provavelmente não. Terei que verificar com o colega que instalou o Discourse inicialmente por que ele inseriu os três.

1 curtida
56

Também estou tendo o erro de locale.

(\u003cunknown\u003e): não encontrou a chave esperada ao analisar um mapeamento de bloco na linha 133, coluna 5 -e LANG=en_US.UTF-8
Erro de sintaxe YAML. Verifique seus arquivos de configuração de containers/*.yml.

Foi causado por um erro de espaçamento na parte inferior do arquivo yml. Corrigi o erro de espaçamento e a atualização foi executada sem problemas.

57

Ao trocar os locais em app.yml, avancei alguns passos, mas infelizmente não muito. Parece que algo ainda está dando errado e a atualização do postgres não está sendo aplicada corretamente:

root@Ubuntu-2204-jammy-amd64-base /var/discourse # ./launcher rebuild app
x86_64 arch detected.
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
Stopping old container
+ /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).
58

Recebi o mesmo erro, ainda está falhando para mim agora também

Eu tentei

  • ./discourse-doctor, mas sem sucesso
  • então pensei que algumas portas estavam sendo usadas, mas o netstats não me mostrou nenhum processo usando essas portas, então reiniciei a instância para ter um novo começo e reconstruí o aplicativo, mas ainda sem sucesso

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!

e

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?
59

parece ser o caso para mim
Acabei de tentar e meu servidor tem este arquivo, e estou tendo falhas na reconstrução

postgres@ubuntu-s-1vcpu-1gb-nyc3-01-app:/var/www/discourse$ ls -al /shared/postgres_run/.s.PGSQL.5432
srwxrwxrwx 1 postgres postgres 0 Fev  2 03:24 /shared/postgres_run/.s.PGSQL.5432
60

Olá @xFocus e @schneeland :wave:

O banco de dados está sendo encerrado de forma limpa quando você para o contêiner app? Os logs devem ser semelhantes à saída em OP.

1 curtida
61

Tentei contornar com este arquivo, mas falhei

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

Em seguida, a reconstrução ainda falha, O cluster de origem não foi desligado corretamente.
@mwaniki

Parando o servidor de banco de dados PostgreSQL 13: main.
Parando o servidor de banco de dados PostgreSQL 15: main.
Realizando Verificações de Consistência
-----------------------------
Verificando versões do cluster                               ok

O cluster de origem não foi desligado corretamente.
Falha, saindo
-------------------------------------------------------------------------------------
FALHA NA ATUALIZAÇÃO DO POSTGRES

Por favor, visite https://meta.discourse.org/t/postgresql-15-update/349515 para suporte.

Você pode executar ./launcher start app para reiniciar seu aplicativo enquanto isso


FALHOU
--------------------
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
 falhou com retorno #<Process::Status: pid 18 exit 1>
Local da falha: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec falhou com os parâmetros {"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 falhou com código de saída 1
** FALHA AO INICIAR ** por favor, role para cima e procure por mensagens de erro anteriores, pode haver mais de uma.
./discourse-doctor pode ajudar a diagnosticar o problema.
931142f4cf49942fb3faf0676818c6395376c9fb6c76008d82037b0b76ae7111
62

Tentei executar iniciar e parar novamente

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

mas eu não tenho este arquivo de log… é preocupante?
obrigado Mwaniki :slight_smile:

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
63

Sim, foi um erro de digitação. Você pode verificar shared/standalone/log/var-log/postgres/current em vez disso? Acabei de atualizar o OP. :slight_smile:

1 curtida
64

Certo, eu não vi o log LOG: database system is shut down

Abaixo está o que tenho depois de executar ./launcher stop app , acho que é por isso que durante minha reconstrução recebi um erro de que a porta do postgre já estava em uso

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 (