| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Version number for pg_control |
| Date: | 2016-07-15 22:22:23 |
| Message-ID: | 16945.1468621343@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Steele <david(at)pgmasters(dot)net> writes:
> +1 for changing it. However, I don't think it's such a big deal since
> each version since 8.3 (at least) has had a unique catalog version.
> Maybe this would affect pg_controldata or other supporting utilities but
> the server itself should not be affected since it also checks the
> catalog version.
Right, that version number exists mostly for the benefit of pg_controldata
and allied utilities. You would get a CRC failure in any case when trying
to go between inconsistent notions of what pg_control contains, but the
version number is supposed to help you figure out why that happened.
As things stand, though, it'd only mislead you.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2016-07-15 22:24:25 | Re: Version number for pg_control |
| Previous Message | Tom Lane | 2016-07-15 22:13:37 | Regression tests vs existing users in an installation |