Update psql lib to postgres version 11.11 #193
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cf-deployment currently uses postgres-release 43, which comes with postgres 11.10.
libpq in capi-release is still on postgres 11.5. According to postgres its best practice to have the client library at least on the level of the server. Newer version of the postgres client / libpq are backward compatible, the server may not be backword compatible. Therefore it would be good to bump libpq in capi-release to the same level as postgres in postgres release. Also the update addresses vulnerabilities in postgres.
We have build a capi-release with the updated libpq, deployed it with bosh-lite and run smoke tests.
This is similar to the PR from one and a half year age: bump libpq to postgres 11.5
You will have to manage the blobstore upload, as we have no access to that.