Previously pdb always permanently cached the database version (via db-metadata) after the first lookup, so it couldn't notice changes. We're likely to adjust that now so that db-metadata always returns the current version.
Consider arranging for pdb to notice and perhaps shut down (or...) if it notices that the postgresql version changes while it's running, since proceeding might be quite risky.
Previously pdb always permanently cached the database version (via db-metadata) after the first lookup, so it couldn't notice changes. We're likely to adjust that now so that db-metadata always returns the current version.
Consider arranging for pdb to notice and perhaps shut down (or...) if it notices that the postgresql version changes while it's running, since proceeding might be quite risky.
One option might be a periodic check like the one we've added for the expected migration level.