diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2023-07-24 17:14:22 +0200 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2023-07-24 17:14:22 +0200 |
| commit | 6061adedf53cbe0f94a52dd02465abf8c7c9fb43 (patch) | |
| tree | b086d5c4cb8fb232c7db304886122cb7f09a137e /src/backend/executor/nodeSubplan.c | |
| parent | e35cc3b3f2d081e2de3a0e077715d12b3580cc74 (diff) | |
| download | postgresql-6061adedf53cbe0f94a52dd02465abf8c7c9fb43.tar.gz postgresql-6061adedf53cbe0f94a52dd02465abf8c7c9fb43.zip | |
Compare only major versions in AdjustUpgrade.pm
Because PostgreSQL::Version is very nuanced about development version
numbers, the comparison to 16beta2 makes it think that that release is
older than 16, therefore applying a database tweak that doesn't work
there (the comparison is only supposed to match when run on version 15).
As suggested by Andrew Dunstan, fix by having AdjustUpgrade.pm public
methods create a separate PostgreSQL::Version object to use for these
comparisons, that only carries the major version number.
While at it, have the same methods ensure that the objects given are of
the expected type.
Backpatch to 16. This module goes all the way back to 9.2, but there's
probably no need for this fix except where betas still live.
Co-authored-by: Andrew Dunstan <andrew@dunslane.net>
Discussion: https://postgr.es/m/20230719110504.zbu74o54bqqlsufb@alvherre.pgsql
Diffstat (limited to 'src/backend/executor/nodeSubplan.c')
0 files changed, 0 insertions, 0 deletions