# עדכון PostgreSQL 13 מ-PostgreSQL 10 נכשל

**URL:** <https://meta.discourse.org/t/postgresql-13-update-from-postgresql-10-fails/192865>\
**Category:** Self-hosting\
**Created:** [6 ביוני,‏ 2021,‏ 5:03pm UTC](https://meta.discourse.org/t/postgresql-13-update-from-postgresql-10-fails/192865 "2021-06-06T17:03:45Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![amotl](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/amotl/32/109873_2.png) [@amotl](https://meta.discourse.org/u/amotl)\
**Post date:** [13 באוקטובר,‏ 2021,‏ 6:38pm UTC](https://meta.discourse.org/t/postgresql-13-update-from-postgresql-10-fails/192865/9 "2021-10-13T18:38:57Z")

</div>

Hi there,

we are in the same situation, yet on a standalone setup. `shared/standalone/log/var-log/` does not display any files at all, however after entering the container, we see identical results:

```plaintext
root@pulp-discourse-iptools:/var/www/discourse# tail -n 3 /var/log/postgres/current
2021-10-13 18:33:04.027 GMT [917] LOG: skipping missing configuration file "/shared/postgres_data/postgresql.auto.conf"
2021-10-13 18:33:04.028 UTC [917] FATAL: data directory "/shared/postgres_data" has wrong ownership
2021-10-13 18:33:04.028 UTC [917] HINT: The server must be started by the user that owns the data directory.

```

```plaintext
root@pulp-discourse-iptools:/var/www/discourse# ls -lan /shared
total 8
drwxr-xr-x 12 0 0 178 Oct 13 18:01 .
drwxr-xr-x 56 0 0 167 May 10 2020 ..
drwxr-xr-x 3 1000 33 21 Apr 3 2019 backups
drwxr-xr-x 4 0 0 34 Apr 3 2019 log
drwxr-xr-x 2 106 110 6 Apr 3 2019 postgres_backup
drwx------ 20 105 109 4096 Oct 13 17:57 postgres_data
drwx------ 19 105 109 4096 Oct 13 18:02 postgres_data_new
drwxrwsr-x 4 105 109 60 Oct 13 17:56 postgres_run
drwxr-xr-x 2 108 111 41 Oct 13 18:26 redis_data
drwxr-xr-x 4 0 0 44 Apr 3 2019 state
drwxr-xr-x 4 1000 33 37 Oct 13 18:26 tmp
drwxr-xr-x 4 1000 33 38 Apr 3 2019 uploads

```

However, that still looks weird:

```plaintext
root@pulp-discourse-iptools:/var/www/discourse# ls -alF /shared | grep postgres_
drwxr-xr-x 2 postgres postgres 6 Apr 3 2019 postgres_backup/
drwx------ 20 Debian-exim ssh 4096 Oct 13 18:53 postgres_data/
drwx------ 19 Debian-exim ssh 4096 Oct 13 18:02 postgres_data_new/
drwxrwsr-x 4 Debian-exim ssh 60 Oct 13 17:56 postgres_run/

```

In order to be more safe than sorry, we switched back to `"templates/postgres.10.template.yml"` in `app.yml` and currently only aim to bring the old instance up again.

Maybe it is sensible to share that we are already on the most recent commit of `https://github.com/discourse/discourse_docker.git`, after switching to the `main` branch. However, because the rebuild did not succeed, this probably has no impact when starting the previous image, right?

If anyone has any idea how to resolve this situation, we would be very grateful. Otherwise, we might come back with further reports.

With kind regards,  
Andreas.

---

_[View the full topic](https://meta.discourse.org/t/postgresql-13-update-from-postgresql-10-fails/192865)._