| From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | Sindhu S <sindhusanti(at)gmail(dot)com> |
| Subject: | Re: Report Postgres Bug - Unlogged table sequence |
| Date: | 2024-08-19 08:57:43 |
| Message-ID: | CAJ7c6TMHbAePVJ5AKschdbG28kLNoCJ60f62dJ=ZgeDQ=wM7Uw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
> Major version upgrade to 15.7 or 16.3 is failing on pg_restore step with following error,
> [...]
To clarify, did you use pg_dump from _newer_ version of PostgreSQL as
recommended[1] ?
"""
It is recommended that you use the pg_dump and pg_dumpall programs
from the newer version of PostgreSQL, to take advantage of
enhancements that might have been made in these programs. Current
releases of the dump programs can read data from any server version
back to 9.2.
"""
[1]: https://www.postgresql.org/docs/current/upgrading.html
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Sargsyan | 2024-08-19 09:40:18 | Re: BUG #18582: fixed range of search for empty slot in SLRU |
| Previous Message | Mathias, Renci | 2024-08-19 07:19:34 | RE: BUG #18569: Memory leak in Postgres Enterprise server |