mirror of
https://github.com/discourse/discourse.git
synced 2026-08-06 04:48:33 +08:00
7c03546b89
pg_dump 17 and later adds SET transaction_timeout = 0 to dumps, but the parameter only exists on PostgreSQL 17+ servers. Restoring such a dump on PostgreSQL 16 or older fails with: psql failed: ERROR: unrecognized configuration parameter "transaction_timeout" This is easy to hit because postgres client tools are commonly newer than the server they talk to (the discourse_docker base image ships the latest client alongside the default version, and pg_dump resolves to the newest one installed), so backups can quietly become un-restorable on the server that created them. Strip the line during restore like the other version-specific SQL in the unwanted_sql list. |
||
|---|---|---|
| .. | ||
| backups | ||
| csv | ||
| db | ||
| emails | ||
| encodings | ||
| feed | ||
| i18n | ||
| images | ||
| json | ||
| md | ||
| media | ||
| mmdb | ||
| multisite | ||
| onebox | ||
| plugins | ||
| scss | ||
| site_settings | ||
| svg | ||
| theme_locales/objects_settings | ||
| theme_settings | ||
| themes | ||
| woff2 | ||
