| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Steele <david(at)pgmasters(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Always bump PG_CONTROL_VERSION? |
| Date: | 2021-05-13 02:04:54 |
| Message-ID: | YJyJRqNoTsbxUb/H@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 12, 2021 at 01:30:27PM -0700, Andres Freund wrote:
> That said, I don't think it's a good practice to use the control file
> version as an identifier for the major version. Who knows, it might be
> necessary to add an optional new format in a minor version at some point
> or such crazyness. And then there's the beta stuff you'd mentioned, etc.
Yes, PG_VERSION, as you wrote upthread already, is already fine for
the job, and FWIW, I have yet to see a case where being able to easily
detect the minor version in a data folder matters.
And, I am of the opinion to not change the control file version if
there is no need to do so.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-05-13 02:12:43 | Re: Performance degradation of REFRESH MATERIALIZED VIEW |
| Previous Message | Julien Rouhaud | 2021-05-13 02:02:45 | Re: compute_query_id and pg_stat_statements |