After upgrading from pgAdmin 4 v9.15 to v9.16, opening the **Properties** dialog for any table on a PostgreSQL 13 server fails.

[lxny2004]

Please note that security bugs or issues should be reported to security@pgadmin.org.

Describe the bug
After upgrading from pgAdmin 4 v9.15 to v9.16, opening the Properties dialog for any table on a PostgreSQL 13 server fails.

The error message is:

column att.attcompression does not exist

The same PostgreSQL server works correctly with pgAdmin 4 v9.15.

This appears to be a regression introduced in v9.16.
A clear and concise description of what the bug is.

To Reproduce

1. Install pgAdmin 4 v9.16.
2. Connect to a PostgreSQL 13.3 server.
3. Expand a database and open the Tables node.
4. Right-click any table.
5. Select Properties.
6. An error dialog appears.

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. See the error

Expected behavior
The table Properties dialog should open successfully, as it did in pgAdmin 4 v9.15.

pgAdmin should remain compatible with PostgreSQL 13, or at least avoid querying catalog columns that do not exist on PostgreSQL 13.

A clear and concise description of what you expected to happen.

Error message
column att.attcompression does not exist

LINE xx:
(CASE WHEN att.attcompression = 'p' THEN 'pglz'
WHEN att.attcompression = 'l' THEN 'lz4'
...

If possible, include the full, unedited text of any error messages displayed.

Screenshots

If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. Windows 10, OSX monterey]
• pgAdmin version: [e.g. 6.15]
• Mode: [e.g Desktop or Server]
• Browser (if running in server mode): [e.g. chrome, safari]
• Package type: [e.g. RPM, DEB, Python, Container, etc.]

Additional context
Additional information:

• The issue affects every table, not just a specific table.
• SQL queries execute normally.
• Browsing table data works normally.
• Only the Properties dialog fails.
• PostgreSQL 13 correctly does not have the pg_catalog.pg_attribute.attcompression column.
• Downgrading to pgAdmin 4 v9.15 immediately resolves the problem.

Add any other context about the problem here.
This looks like a regression because the same PostgreSQL 13.3 server works correctly with pgAdmin 4 v9.15 but fails immediately after upgrading to v9.16.

Environment

• pgAdmin version: 9.16
• Previous working version: 9.15
• PostgreSQL version: 13.3
• server_version_num: 130003
• Operating System: Windows 11 x64
• Installation: Official PostgreSQL server + official pgAdmin installer

[robe2]

I think this might be an intentional drop since PG13 was end of lifed last year.

The 9.16 release notes have under the house keeping section:

Rebase version-specific SQL templates so the default targets PostgreSQL 14, the oldest supported server version, dropping obsolete sub-14 template buckets.