Minimum supported version 9.3.3 must be checked

[dzhus]

As of now the default PostgreSQL version requirement is too lax for the default configuration file included. The config produced by the role may fail to work because *multixact* family of settings was introduced only in 9.3.3 (https://www.postgresql.org/docs/9.3/static/release-9-3-3.html):

LOG:  unrecognized configuration parameter "autovacuum_multixact_freeze_max_age" in file "/etc/postgresql/9.3/main/postgresql.conf" line 468
LOG:  unrecognized configuration parameter "vacuum_multixact_freeze_min_age" in file "/etc/postgresql/9.3/main/postgresql.conf" line 498
LOG:  unrecognized configuration parameter "vacuum_multixact_freeze_table_age" in file "/etc/postgresql/9.3/main/postgresql.conf" line 499

I was rolling the role out to a server which had 9.3.0 installed and it obviously failed.

[aoyawale]

is this still an issue?

[gclough]

Considering that v9.3.2 was superseded by v9.3.3 on 20/Feb/2014, (4 years and 19 patches ago)... I'd say we don't need to bother coding for this situation, because nobody should be using that version. Serious security patches since then have been:

• Heartbleed
• Meltdown
• Uncontrolled Search Path (Score: 8.8)

The list is shocking, so I'd say we're safe to assume nobody in their right mind would still be running v9.3.0 thru v9.3.2:

https://www.postgresql.org/support/security/9.3/