Behal) E.36. Release 6.5 Release date: 1999-06-09 This release marks a major step in the development team’s mastery of the source code we inherited from Berkeley. You will see we are now easily adding major major features, thanks to the increasing size and experi- ence of our world-wide development team. Here is a brief summary of the more notable changes: 1301 Appendix E. Release Notes Multiversion concurrency command. Speedups We continue to speed up PostgreSQL, thanks to the variety of talents within our team. We have sped up memory allocation, optimization, table joins, and row transfer routines. Ports

Behal) E.36. Release 6.5 Release date: 1999-06-09 This release marks a major step in the development team’s mastery of the source code we inherited from Berkeley. You will see we are now easily adding major major features, thanks to the increasing size and experience of our world-wide development team. Here is a brief summary of the more notable changes: Multiversion concurrency control(MVCC) This removes command. Speedups We continue to speed up PostgreSQL, thanks to the variety of talents within our team. We have sped up memory allocation, optimization, table joins, and row transfer routines. Ports

security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit E.148. Release 6.5 Release date: 1999-06-09 This release marks a major step in the development team’s mastery of the source code we inherited from Berkeley. You will see we are now easily adding major major features, thanks to the increasing size and experi- ence of our world-wide development team. Here is a brief summary of the more notable changes: Multiversion concurrency control(MVCC) This removes

security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit

security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit

security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit

security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit

Behal) E.91. Release 6.5 Release date: 1999-06-09 This release marks a major step in the development team’s mastery of the source code we inherited from Berkeley. You will see we are now easily adding major major features, thanks to the increasing size and experi- ence of our world-wide development team. Here is a brief summary of the more notable changes: Multiversion concurrency control(MVCC) This removes command. Speedups We continue to speed up PostgreSQL, thanks to the variety of talents within our team. We have sped up memory allocation, optimization, table joins, and row transfer routines. Ports

Behal) E.49. Release 6.5 Release date: 1999-06-09 This release marks a major step in the development team’s mastery of the source code we inherited from Berkeley. You will see we are now easily adding major major features, thanks to the increasing size and experi- ence of our world-wide development team. Here is a brief summary of the more notable changes: Multiversion concurrency control(MVCC) This removes command. Speedups We continue to speed up PostgreSQL, thanks to the variety of talents within our team. We have sped up memory allocation, optimization, table joins, and row transfer routines. Ports

security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit security risk since the function’s return address could be overwritten. Thanks to Apple Inc’s security team for reporting this issue and supplying the fix. (CVE-2010-4015) • Fix bug in contrib/seg’s GiST picksplit E.173. Release 6.5 Release date: 1999-06-09 This release marks a major step in the development team’s mastery of the source code we inherited from Berkeley. You will see we are now easily adding major