This bug was fixed in the package postgresql-9.5 - 9.5.21-0ubuntu0.16.04.1
--------------- postgresql-9.5 (9.5.21-0ubuntu0.16.04.1) xenial; urgency=medium
* New upstream release (LP: #1863108) - A dump/restore is not required however, if you use the contrib/intarray extension with a GiST index, and you rely on indexed searches for the <@ operator, see the release notes for details in regard to a related fix. - Details about these and many further changes can be found at: https://www.postgresql.org/docs/9.5/static/release-9-5-20.html https://www.postgresql.org/docs/9.5/static/release-9-5-21.html
-- Christian Ehrhardt <email address hidden> Thu, 13 Feb 2020 15:18:20 +0100
This bug was fixed in the package postgresql-9.5 - 9.5.21- 0ubuntu0. 16.04.1
--------------- 0ubuntu0. 16.04.1) xenial; urgency=medium
postgresql-9.5 (9.5.21-
* New upstream release (LP: #1863108) /www.postgresql .org/docs/ 9.5/static/ release- 9-5-20. html /www.postgresql .org/docs/ 9.5/static/ release- 9-5-21. html
- A dump/restore is not required however, if you use the contrib/intarray
extension with a GiST index, and you rely on indexed searches for the <@
operator, see the release notes for details in regard to a related fix.
- Details about these and many further changes can be found at:
https:/
https:/
-- Christian Ehrhardt <email address hidden> Thu, 13 Feb 2020 15:18:20 +0100