Document required PostgreSQL role privileges for TTS database migrations

[Copilot]

Migration docs described how to run TTS migration commands but not the PostgreSQL privilege level required to execute them successfully. This update clarifies the required DB role to reduce migration failures caused by under-privileged users.

• What changed

  • Added a warning note in Docker upgrade migration docs:
    • Path: doc/content/enterprise/docker/upgrading/_index.md
  • Clarified that migrations must run with:
    • the PostgreSQL role that owns existing TTS tables, or
    • a PostgreSQL superuser
  • Explicitly called out that migrations execute DDL (CREATE, ALTER, DROP), so read/write-only table grants are insufficient.

• Doc example added

{{< warning >}}
For PostgreSQL deployments, run migrations with the same PostgreSQL role that owns the existing {{< tts >}} tables (or with a superuser role). Migrations execute DDL statements such as `CREATE`, `ALTER` and `DROP`, so a role with only read/write table privileges is not sufficient.
{{< /warning >}}

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• ttui.thethingsindustries.com
  • Triggering command: /usr/local/bin/node node /usr/local/bin/yarn --cwd doc -m elf_x86_64 --hash-style=gnu --as-needed -dynamic-linker /lib64/ld-linux-x86-64.so.2 -z relro -I /libsass @v0.139.4/config/tmp/go-build510302698/b572/ src/include -I om/bep/gowebp@v0--source 2o x64/pkg/tool/lin--destination (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[vlasebian]