| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>, "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 18:47:23 |
| Message-ID: | 1b2452e3-a15a-d760-4db2-3b7db5e18a89@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 5/31/22 12:21 PM, Tom Lane wrote:
> "Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
>> On 5/31/22 10:55 AM, Tom Lane wrote:
>>> 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.
>
> Further investigation shows that we've failed to update this twice in
> the past six years, and failed to update a similar comment about psql
> once. I fixed 'em, but I have very little hope that they'll stay fixed.
Could we add as part of the branching procedure that we update this value?
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2022-05-31 20:03:16 | Re: Should we really recommend "-A md5 or -A password"? |
| Previous Message | Gustavo | 2022-05-31 16:58:24 | Re: CREATE EXTENSION not adding extension on second SCHEMA |