Pgsql's parameters - for message types like StartupMessage and
ParameterStatus, for instance, don't have a finite, definitive set, as
per their documentation. Our json schema was allow expecting a fixed set
of parameters, though, resulting in SV tests failing if different, valid
parameters appeared.
Bug #5579
"startup_parameters": {
"type": "object",
"properties": {
- "database": {
- "type": "string"
- },
"optional_parameters": {
"type": "array",
"items": {
"client_encoding": {
"type": "string"
},
+ "database": {
+ "type": "string"
+ },
+ "datestyle": {
+ "type": "string"
+ },
+ "extra_float_digits": {
+ "type": "string"
+ },
+ "options": {
+ "type": "string"
+ },
"replication": {
"type": "string"
}
},
- "additionalProperties": false
+ "additionalProperties": true
}
},
"user": {
"type": "string"
}
},
- "additionalProperties": false
+ "additionalProperties": true
}
},
"process_id": {