| From: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Can we still dump version 7? |
| Date: | 2022-05-31 16:04:40 |
| Message-ID: | GV0P278MB04195040552F6D771D1A6837D2DC9@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
>>
>> Ugh, missed that, thanks for spotting it.
>> I wonder whether we should update this or just remove it --- it's
>> clearly something that's likely to get missed again.
>While burdensome, +1 for updating. We don't want users to get caught by
>surprise if pg_dumpall does not work on an old version when trying to
>update to a newer version.
What about something like this:
"Current releases of the dump programs can read data from any supported version of PostgreSQL. You can expect the last XXX unsupported versions to work as well. If you cannot dump your version of PostgreSQL with the current releases you need to take an extra step and use a version of the dump programs which can still read from your old release."
That would remove the version number and there is no risk we miss it again in the future. I am not sure about the official policy for that, though.
Regards
Daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-05-31 16:21:09 | Re: Can we still dump version 7? |
| Previous Message | Tom Lane | 2022-05-31 15:32:57 | Re: CREATE EXTENSION not adding extension on second SCHEMA |