<?xml version="1.0" encoding="UTF-8"?>
<otherdata xmlns="http://linux.duke.edu/metadata/other" packages="371">
<package pkgid="bab50504950503bdc30f23e61d51a50b1013d82dc945cbb913d19c95226fa4dc" name="PgTcl" arch="src">
  <version epoch="0" ver="1.7" rel="375.2"/>
  <changelog author="max@suse.de" date="1043668800">- Renamed from postgresql-tcl to PgTcl.
- New version: 1.4b3
- This becomes a package of it's own, because libpgtcl
  has become a separate project.</changelog>
  <changelog author="max@suse.de" date="1069156800">- Enabled building as a non-root user.</changelog>
  <changelog author="max@suse.de" date="1078488000">- Added patch to current CVS head.</changelog>
  <changelog author="max@suse.de" date="1080820800">- Added heimdal-lib to neededforbuild to fix the creation
  of pkgIndex.tcl.</changelog>
  <changelog author="max@suse.de" date="1088769600">- Updated to the final 1.4 release.</changelog>
  <changelog author="ro@suse.de" date="1100779200">- use kerberos-devel-packages</changelog>
  <changelog author="max@suse.de" date="1122552000">- New version: 1.5.
- Move script library to /usr/share/tcl .</changelog>
  <changelog author="max@suse.de" date="1134475200">- Fixed a typo in tcl.m4 that broke configure with bash 3.1.</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="jengelh@medozas.de" date="1316260800">- Remove redundant tags/sections from specfile
- Use %_smp_mflags for parallel build</changelog>
  <changelog author="coolo@suse.com" date="1324382400">- add autoconf as buildrequire to avoid implicit dependency</changelog>
  <changelog author="max@suse.com" date="1326283200">- Update to version 1.7 to fix an issue with Tcl 8.5 (bnc#739978).</changelog>
  <changelog author="max@suse.com" date="1375272000">- Set -DUSE_INTERP_ERRORLINE to fix build with Tcl 8.6.</changelog>
  <changelog author="max@suse.com" date="1380715200">- Avoid an unneeded explicit dependency on a certain version of
  libtcl (pgtcl-stubs.patch).</changelog>
</package>
<package pkgid="82d4314dd3af466c76e320d8abf0aa7ef305ebb72ecaf57b20c281f8fa9abbd5" name="PgTcl" arch="x86_64">
  <version epoch="0" ver="1.7" rel="375.2"/>
  <changelog author="max@suse.de" date="1088769600">- Updated to the final 1.4 release.</changelog>
  <changelog author="ro@suse.de" date="1100779200">- use kerberos-devel-packages</changelog>
  <changelog author="max@suse.de" date="1122552000">- New version: 1.5.
- Move script library to /usr/share/tcl .</changelog>
  <changelog author="max@suse.de" date="1134475200">- Fixed a typo in tcl.m4 that broke configure with bash 3.1.</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="jengelh@medozas.de" date="1316260800">- Remove redundant tags/sections from specfile
- Use %_smp_mflags for parallel build</changelog>
  <changelog author="coolo@suse.com" date="1324382400">- add autoconf as buildrequire to avoid implicit dependency</changelog>
  <changelog author="max@suse.com" date="1326283200">- Update to version 1.7 to fix an issue with Tcl 8.5 (bnc#739978).</changelog>
  <changelog author="max@suse.com" date="1375272000">- Set -DUSE_INTERP_ERRORLINE to fix build with Tcl 8.6.</changelog>
  <changelog author="max@suse.com" date="1380715200">- Avoid an unneeded explicit dependency on a certain version of
  libtcl (pgtcl-stubs.patch).</changelog>
</package>
<package pkgid="2be96f687792fb749e9b82a3e84b01c57a5e05e8d79772a2a44ab0b25d771b2e" name="PgTcl-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.7" rel="375.2"/>
  <changelog author="max@suse.de" date="1043668800">- Renamed from postgresql-tcl to PgTcl.
- New version: 1.4b3
- This becomes a package of it's own, because libpgtcl
  has become a separate project.</changelog>
  <changelog author="max@suse.de" date="1069156800">- Enabled building as a non-root user.</changelog>
  <changelog author="max@suse.de" date="1078488000">- Added patch to current CVS head.</changelog>
  <changelog author="max@suse.de" date="1080820800">- Added heimdal-lib to neededforbuild to fix the creation
  of pkgIndex.tcl.</changelog>
  <changelog author="max@suse.de" date="1088769600">- Updated to the final 1.4 release.</changelog>
  <changelog author="ro@suse.de" date="1100779200">- use kerberos-devel-packages</changelog>
  <changelog author="max@suse.de" date="1122552000">- New version: 1.5.
- Move script library to /usr/share/tcl .</changelog>
  <changelog author="max@suse.de" date="1134475200">- Fixed a typo in tcl.m4 that broke configure with bash 3.1.</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="jengelh@medozas.de" date="1316260800">- Remove redundant tags/sections from specfile
- Use %_smp_mflags for parallel build</changelog>
  <changelog author="coolo@suse.com" date="1324382400">- add autoconf as buildrequire to avoid implicit dependency</changelog>
  <changelog author="max@suse.com" date="1326283200">- Update to version 1.7 to fix an issue with Tcl 8.5 (bnc#739978).</changelog>
  <changelog author="max@suse.com" date="1375272000">- Set -DUSE_INTERP_ERRORLINE to fix build with Tcl 8.6.</changelog>
  <changelog author="max@suse.com" date="1380715200">- Avoid an unneeded explicit dependency on a certain version of
  libtcl (pgtcl-stubs.patch).</changelog>
</package>
<package pkgid="a0b2ffbce9c59734de765c1f39c0f44a63aff0dc34b60bf923805275647432ed" name="PyGreSQL" arch="src">
  <version epoch="0" ver="4.1.1" rel="407.2"/>
  <changelog author="max@suse.de" date="1078488000">- Package postgresql-python separated from the PostgreSQL source
  RPM and renamed to PyGreSQL to reflect the fact, that it is a
  separete project now.
- Version: 3.4</changelog>
  <changelog author="max@suse.de" date="1079697600">- Add a dependency to python (bug #36499).</changelog>
  <changelog author="max@suse.de" date="1106827200">- New version: 3.6.1</changelog>
  <changelog author="tarnold@suse.de" date="1120478400">- Neew vrsion: 3.6.2</changelog>
  <changelog author="max@suse.de" date="1136462400">- New version: 3.7</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="kukuk@suse.de" date="1141473600">- updated to reflect python changes due to #149809</changelog>
  <changelog author="max@suse.de" date="1153828800">- New version: 3.8.1
- Use string methods instead of deprecated string functions.
- Only use SQL-standard way of escaping quotes.
- Added the functions escape_string() and escape/unescape_bytea().
- Reverted code in clear() method that set date to current.
- Added code for backwards compatibility in OID munging code.
- Reorder attnames tests so that "interval" is checked for before
  "int."
- If caller supplies key dictionary, make sure that all has a
  namespace.
- Installed new favicon.ico from Matthew Sporleder &lt;mspo@mspo.com&gt;
- Replaced snprintf by PyOS_snprintf.
- Removed NO_SNPRINTF switch which is not needed any longer
- Clean up some variable names and namespace
- Add get_relations() method to get any type of relation
- Rewrite get_tables() to use get_relations()
- Use new method in get_attnames method to get attributes of views
  as well
- Add Binary type
- Number of rows is now -1 after executing no-result statements
- Fix some number handling
- Non-simple types do not raise an error any more
- Improvements to documentation framework
- Take into account that nowadays not every table must have an oid
  column
- Simplification and improvement of the inserttable() function
- Fix up unit tests
- The usual assortment of minor fixes and enhancements</changelog>
  <changelog author="nkrinner@novell.com" date="1299240000">- New version: 4.0
- Dropped support for Python below 2.3 and PostgreSQL below 7.4.
- Improved performance of fetchall() for large result sets by
  speeding up the type casts (as suggested by Peter Schuller).
- Exposed exceptions as attributes of the connection object.
- Exposed connection as attribute of the cursor object.
- Cursors now support the iteration protocol.
- Added new method to get parameter settings.
- Added customizable row_factory as suggested by Simon Pamies.
- Separated between mandatory and additional type objects.
- Added keyword args to insert, update and delete methods.
- Added exception handling for direct copy.
- Start transactions only when necessary, not after every commit().
- Release the GIL while making a connection (as suggested by Peter
  Schuller).
- If available, use decimal.Decimal for numeric types.
- Allow DB wrapper to be used with DB-API 2 connections (as
  suggested by Chris Hilton).
- Made private attributes of DB wrapper accessible.
- Dropped dependence on mx.DateTime module.
- Support for PQescapeStringConn() and PQescapeByteaConn(); these
  are now also used by the internal _quote() functions.
- Added 'int8' to INTEGER types. New SMALLINT type.
- Added a way to find the number of rows affected by a query()
  with the classic pg module by returning it as a string. For single
  inserts, query() still returns the oid as an integer. The pgdb
  module already provides the "rowcount" cursor attribute for the
  same purpose.
- Improved getnotify() by calling PQconsumeInput() instead of
  submitting an empty command.
- Removed compatibility code for old OID munging style.
- The insert() and update() methods now use the "returning" clause
  if possible to get all changed values, and they also check in
  advance whether a subsequent select is possible, so that ongoing
  transactions won't break if there is no select privilege.
- Added "protocol_version" and "server_version" attributes.
- Revived the "user" attribute.
- The pg module now works correctly with composite primary keys;
  these are represented as frozensets.
- Removed the undocumented and actually unnecessary "view"
  parameter from the get() method.
- get() raises a nicer ProgrammingError instead of a KeyError if
  no primary key was found.
- delete() now also works based on the primary key if no oid
  available and returns whether the row existed or not.</changelog>
  <changelog author="jengelh@medozas.de" date="1316260800">- Remove redundant tags/sections from specfile</changelog>
  <changelog author="p.drouand@gmail.com" date="1418472000">- Clean up specfile
- Use download Url as source
- Update to version 4.1.1
  + Add WhenNotified class and method.  Replaces need for third party
    pgnotify.
  + Sharpen test for inserting current_timestamp.
  + Add more quote tests.  False and 0 should evaluate to NULL.
  + More tests   + Any number other than 0 is True.
  + Do not use positional parameters internally.
    This restores backward compatibility with version 4.0.
  + Add methods for changing the decimal point.
- Changes from version 4.1
  + Dropped support for Python below 2.5 and PostgreSQL below 8.3.
  + Added support for Python up to 2.7 and PostgreSQL up to 9.2.
  + Particularly, support PQescapeLiteral() and PQescapeIdentifier().
  + The query method of the classic API now supports positional parameters.
    This an effective way to pass arbitrary or unknown data without worrying
    about SQL injection or syntax errors
  + The classic API now supports a method namedresult() in addition to
    getresult() and dictresult(), which returns the rows of the result
    as named tuples if these are supported (Python 2.6 or higher).
  + The classic API has got the new methods begin(), commit(), rollback(),
    savepoint() and release() for handling transactions.
  + Both classic and DBAPI 2 connections can now be used as context
    managers for encapsulating transactions.
  + The execute() and executemany() methods now return the cursor object,
    so you can now write statements like "for row in cursor.execute(...)"
  + Binary objects are now automatically escaped and unescaped.
  + Bug in money quoting fixed.  Amounts of $0.00 handled correctly.
  + Proper handling of date and time objects as input.
  + Proper handling of floats with 'nan' or 'inf' values as input.
  + Fixed the set_decimal() function.
  + All DatabaseError instances now have a sqlstate attribute.
  + The getnotify() method can now also return payload strings (#15).
  + Better support for notice processing with the new methods
    set_notice_receiver() and get_notice_receiver()
  + Open transactions are rolled back when pgdb connections are closed
  + Connections and cursors can now be used with the "with" statement
  + New method use_regtypes() that can be called to let getattnames()
  return regular type names instead of the simplified classic types (#44).
- Fix Provides/Obsoletes tags</changelog>
</package>
<package pkgid="1aad8da97c66e50c91fcf998ec94ddc3943f8f4c4e4267f469819fcd68b1e599" name="PyGreSQL" arch="x86_64">
  <version epoch="0" ver="4.1.1" rel="407.2"/>
  <changelog author="max@suse.de" date="1079697600">- Add a dependency to python (bug #36499).</changelog>
  <changelog author="max@suse.de" date="1106827200">- New version: 3.6.1</changelog>
  <changelog author="tarnold@suse.de" date="1120478400">- Neew vrsion: 3.6.2</changelog>
  <changelog author="max@suse.de" date="1136462400">- New version: 3.7</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="kukuk@suse.de" date="1141473600">- updated to reflect python changes due to #149809</changelog>
  <changelog author="max@suse.de" date="1153828800">- New version: 3.8.1
- Use string methods instead of deprecated string functions.
- Only use SQL-standard way of escaping quotes.
- Added the functions escape_string() and escape/unescape_bytea().
- Reverted code in clear() method that set date to current.
- Added code for backwards compatibility in OID munging code.
- Reorder attnames tests so that "interval" is checked for before
  "int."
- If caller supplies key dictionary, make sure that all has a
  namespace.
- Installed new favicon.ico from Matthew Sporleder &lt;mspo@mspo.com&gt;
- Replaced snprintf by PyOS_snprintf.
- Removed NO_SNPRINTF switch which is not needed any longer
- Clean up some variable names and namespace
- Add get_relations() method to get any type of relation
- Rewrite get_tables() to use get_relations()
- Use new method in get_attnames method to get attributes of views
  as well
- Add Binary type
- Number of rows is now -1 after executing no-result statements
- Fix some number handling
- Non-simple types do not raise an error any more
- Improvements to documentation framework
- Take into account that nowadays not every table must have an oid
  column
- Simplification and improvement of the inserttable() function
- Fix up unit tests
- The usual assortment of minor fixes and enhancements</changelog>
  <changelog author="nkrinner@novell.com" date="1299240000">- New version: 4.0
- Dropped support for Python below 2.3 and PostgreSQL below 7.4.
- Improved performance of fetchall() for large result sets by
  speeding up the type casts (as suggested by Peter Schuller).
- Exposed exceptions as attributes of the connection object.
- Exposed connection as attribute of the cursor object.
- Cursors now support the iteration protocol.
- Added new method to get parameter settings.
- Added customizable row_factory as suggested by Simon Pamies.
- Separated between mandatory and additional type objects.
- Added keyword args to insert, update and delete methods.
- Added exception handling for direct copy.
- Start transactions only when necessary, not after every commit().
- Release the GIL while making a connection (as suggested by Peter
  Schuller).
- If available, use decimal.Decimal for numeric types.
- Allow DB wrapper to be used with DB-API 2 connections (as
  suggested by Chris Hilton).
- Made private attributes of DB wrapper accessible.
- Dropped dependence on mx.DateTime module.
- Support for PQescapeStringConn() and PQescapeByteaConn(); these
  are now also used by the internal _quote() functions.
- Added 'int8' to INTEGER types. New SMALLINT type.
- Added a way to find the number of rows affected by a query()
  with the classic pg module by returning it as a string. For single
  inserts, query() still returns the oid as an integer. The pgdb
  module already provides the "rowcount" cursor attribute for the
  same purpose.
- Improved getnotify() by calling PQconsumeInput() instead of
  submitting an empty command.
- Removed compatibility code for old OID munging style.
- The insert() and update() methods now use the "returning" clause
  if possible to get all changed values, and they also check in
  advance whether a subsequent select is possible, so that ongoing
  transactions won't break if there is no select privilege.
- Added "protocol_version" and "server_version" attributes.
- Revived the "user" attribute.
- The pg module now works correctly with composite primary keys;
  these are represented as frozensets.
- Removed the undocumented and actually unnecessary "view"
  parameter from the get() method.
- get() raises a nicer ProgrammingError instead of a KeyError if
  no primary key was found.
- delete() now also works based on the primary key if no oid
  available and returns whether the row existed or not.</changelog>
  <changelog author="jengelh@medozas.de" date="1316260800">- Remove redundant tags/sections from specfile</changelog>
  <changelog author="p.drouand@gmail.com" date="1418472000">- Clean up specfile
- Use download Url as source
- Update to version 4.1.1
  + Add WhenNotified class and method.  Replaces need for third party
    pgnotify.
  + Sharpen test for inserting current_timestamp.
  + Add more quote tests.  False and 0 should evaluate to NULL.
  + More tests   + Any number other than 0 is True.
  + Do not use positional parameters internally.
    This restores backward compatibility with version 4.0.
  + Add methods for changing the decimal point.
- Changes from version 4.1
  + Dropped support for Python below 2.5 and PostgreSQL below 8.3.
  + Added support for Python up to 2.7 and PostgreSQL up to 9.2.
  + Particularly, support PQescapeLiteral() and PQescapeIdentifier().
  + The query method of the classic API now supports positional parameters.
    This an effective way to pass arbitrary or unknown data without worrying
    about SQL injection or syntax errors
  + The classic API now supports a method namedresult() in addition to
    getresult() and dictresult(), which returns the rows of the result
    as named tuples if these are supported (Python 2.6 or higher).
  + The classic API has got the new methods begin(), commit(), rollback(),
    savepoint() and release() for handling transactions.
  + Both classic and DBAPI 2 connections can now be used as context
    managers for encapsulating transactions.
  + The execute() and executemany() methods now return the cursor object,
    so you can now write statements like "for row in cursor.execute(...)"
  + Binary objects are now automatically escaped and unescaped.
  + Bug in money quoting fixed.  Amounts of $0.00 handled correctly.
  + Proper handling of date and time objects as input.
  + Proper handling of floats with 'nan' or 'inf' values as input.
  + Fixed the set_decimal() function.
  + All DatabaseError instances now have a sqlstate attribute.
  + The getnotify() method can now also return payload strings (#15).
  + Better support for notice processing with the new methods
    set_notice_receiver() and get_notice_receiver()
  + Open transactions are rolled back when pgdb connections are closed
  + Connections and cursors can now be used with the "with" statement
  + New method use_regtypes() that can be called to let getattnames()
  return regular type names instead of the simplified classic types (#44).
- Fix Provides/Obsoletes tags</changelog>
</package>
<package pkgid="6b16d342f57fa13ab5b69696f607a9bf5587765a354c018aae4d814cef3a058d" name="PyGreSQL-debuginfo" arch="x86_64">
  <version epoch="0" ver="4.1.1" rel="407.2"/>
  <changelog author="max@suse.de" date="1078488000">- Package postgresql-python separated from the PostgreSQL source
  RPM and renamed to PyGreSQL to reflect the fact, that it is a
  separete project now.
- Version: 3.4</changelog>
  <changelog author="max@suse.de" date="1079697600">- Add a dependency to python (bug #36499).</changelog>
  <changelog author="max@suse.de" date="1106827200">- New version: 3.6.1</changelog>
  <changelog author="tarnold@suse.de" date="1120478400">- Neew vrsion: 3.6.2</changelog>
  <changelog author="max@suse.de" date="1136462400">- New version: 3.7</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="kukuk@suse.de" date="1141473600">- updated to reflect python changes due to #149809</changelog>
  <changelog author="max@suse.de" date="1153828800">- New version: 3.8.1
- Use string methods instead of deprecated string functions.
- Only use SQL-standard way of escaping quotes.
- Added the functions escape_string() and escape/unescape_bytea().
- Reverted code in clear() method that set date to current.
- Added code for backwards compatibility in OID munging code.
- Reorder attnames tests so that "interval" is checked for before
  "int."
- If caller supplies key dictionary, make sure that all has a
  namespace.
- Installed new favicon.ico from Matthew Sporleder &lt;mspo@mspo.com&gt;
- Replaced snprintf by PyOS_snprintf.
- Removed NO_SNPRINTF switch which is not needed any longer
- Clean up some variable names and namespace
- Add get_relations() method to get any type of relation
- Rewrite get_tables() to use get_relations()
- Use new method in get_attnames method to get attributes of views
  as well
- Add Binary type
- Number of rows is now -1 after executing no-result statements
- Fix some number handling
- Non-simple types do not raise an error any more
- Improvements to documentation framework
- Take into account that nowadays not every table must have an oid
  column
- Simplification and improvement of the inserttable() function
- Fix up unit tests
- The usual assortment of minor fixes and enhancements</changelog>
  <changelog author="nkrinner@novell.com" date="1299240000">- New version: 4.0
- Dropped support for Python below 2.3 and PostgreSQL below 7.4.
- Improved performance of fetchall() for large result sets by
  speeding up the type casts (as suggested by Peter Schuller).
- Exposed exceptions as attributes of the connection object.
- Exposed connection as attribute of the cursor object.
- Cursors now support the iteration protocol.
- Added new method to get parameter settings.
- Added customizable row_factory as suggested by Simon Pamies.
- Separated between mandatory and additional type objects.
- Added keyword args to insert, update and delete methods.
- Added exception handling for direct copy.
- Start transactions only when necessary, not after every commit().
- Release the GIL while making a connection (as suggested by Peter
  Schuller).
- If available, use decimal.Decimal for numeric types.
- Allow DB wrapper to be used with DB-API 2 connections (as
  suggested by Chris Hilton).
- Made private attributes of DB wrapper accessible.
- Dropped dependence on mx.DateTime module.
- Support for PQescapeStringConn() and PQescapeByteaConn(); these
  are now also used by the internal _quote() functions.
- Added 'int8' to INTEGER types. New SMALLINT type.
- Added a way to find the number of rows affected by a query()
  with the classic pg module by returning it as a string. For single
  inserts, query() still returns the oid as an integer. The pgdb
  module already provides the "rowcount" cursor attribute for the
  same purpose.
- Improved getnotify() by calling PQconsumeInput() instead of
  submitting an empty command.
- Removed compatibility code for old OID munging style.
- The insert() and update() methods now use the "returning" clause
  if possible to get all changed values, and they also check in
  advance whether a subsequent select is possible, so that ongoing
  transactions won't break if there is no select privilege.
- Added "protocol_version" and "server_version" attributes.
- Revived the "user" attribute.
- The pg module now works correctly with composite primary keys;
  these are represented as frozensets.
- Removed the undocumented and actually unnecessary "view"
  parameter from the get() method.
- get() raises a nicer ProgrammingError instead of a KeyError if
  no primary key was found.
- delete() now also works based on the primary key if no oid
  available and returns whether the row existed or not.</changelog>
  <changelog author="jengelh@medozas.de" date="1316260800">- Remove redundant tags/sections from specfile</changelog>
  <changelog author="p.drouand@gmail.com" date="1418472000">- Clean up specfile
- Use download Url as source
- Update to version 4.1.1
  + Add WhenNotified class and method.  Replaces need for third party
    pgnotify.
  + Sharpen test for inserting current_timestamp.
  + Add more quote tests.  False and 0 should evaluate to NULL.
  + More tests   + Any number other than 0 is True.
  + Do not use positional parameters internally.
    This restores backward compatibility with version 4.0.
  + Add methods for changing the decimal point.
- Changes from version 4.1
  + Dropped support for Python below 2.5 and PostgreSQL below 8.3.
  + Added support for Python up to 2.7 and PostgreSQL up to 9.2.
  + Particularly, support PQescapeLiteral() and PQescapeIdentifier().
  + The query method of the classic API now supports positional parameters.
    This an effective way to pass arbitrary or unknown data without worrying
    about SQL injection or syntax errors
  + The classic API now supports a method namedresult() in addition to
    getresult() and dictresult(), which returns the rows of the result
    as named tuples if these are supported (Python 2.6 or higher).
  + The classic API has got the new methods begin(), commit(), rollback(),
    savepoint() and release() for handling transactions.
  + Both classic and DBAPI 2 connections can now be used as context
    managers for encapsulating transactions.
  + The execute() and executemany() methods now return the cursor object,
    so you can now write statements like "for row in cursor.execute(...)"
  + Binary objects are now automatically escaped and unescaped.
  + Bug in money quoting fixed.  Amounts of $0.00 handled correctly.
  + Proper handling of date and time objects as input.
  + Proper handling of floats with 'nan' or 'inf' values as input.
  + Fixed the set_decimal() function.
  + All DatabaseError instances now have a sqlstate attribute.
  + The getnotify() method can now also return payload strings (#15).
  + Better support for notice processing with the new methods
    set_notice_receiver() and get_notice_receiver()
  + Open transactions are rolled back when pgdb connections are closed
  + Connections and cursors can now be used with the "with" statement
  + New method use_regtypes() that can be called to let getattnames()
  return regular type names instead of the simplified classic types (#44).
- Fix Provides/Obsoletes tags</changelog>
</package>
<package pkgid="120549ab1e30918c765def09ff79cca1a4257b2cce5a7075e71ea56dea4a1d89" name="PyGreSQL-debugsource" arch="x86_64">
  <version epoch="0" ver="4.1.1" rel="407.2"/>
  <changelog author="max@suse.de" date="1079697600">- Add a dependency to python (bug #36499).</changelog>
  <changelog author="max@suse.de" date="1106827200">- New version: 3.6.1</changelog>
  <changelog author="tarnold@suse.de" date="1120478400">- Neew vrsion: 3.6.2</changelog>
  <changelog author="max@suse.de" date="1136462400">- New version: 3.7</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="kukuk@suse.de" date="1141473600">- updated to reflect python changes due to #149809</changelog>
  <changelog author="max@suse.de" date="1153828800">- New version: 3.8.1
- Use string methods instead of deprecated string functions.
- Only use SQL-standard way of escaping quotes.
- Added the functions escape_string() and escape/unescape_bytea().
- Reverted code in clear() method that set date to current.
- Added code for backwards compatibility in OID munging code.
- Reorder attnames tests so that "interval" is checked for before
  "int."
- If caller supplies key dictionary, make sure that all has a
  namespace.
- Installed new favicon.ico from Matthew Sporleder &lt;mspo@mspo.com&gt;
- Replaced snprintf by PyOS_snprintf.
- Removed NO_SNPRINTF switch which is not needed any longer
- Clean up some variable names and namespace
- Add get_relations() method to get any type of relation
- Rewrite get_tables() to use get_relations()
- Use new method in get_attnames method to get attributes of views
  as well
- Add Binary type
- Number of rows is now -1 after executing no-result statements
- Fix some number handling
- Non-simple types do not raise an error any more
- Improvements to documentation framework
- Take into account that nowadays not every table must have an oid
  column
- Simplification and improvement of the inserttable() function
- Fix up unit tests
- The usual assortment of minor fixes and enhancements</changelog>
  <changelog author="nkrinner@novell.com" date="1299240000">- New version: 4.0
- Dropped support for Python below 2.3 and PostgreSQL below 7.4.
- Improved performance of fetchall() for large result sets by
  speeding up the type casts (as suggested by Peter Schuller).
- Exposed exceptions as attributes of the connection object.
- Exposed connection as attribute of the cursor object.
- Cursors now support the iteration protocol.
- Added new method to get parameter settings.
- Added customizable row_factory as suggested by Simon Pamies.
- Separated between mandatory and additional type objects.
- Added keyword args to insert, update and delete methods.
- Added exception handling for direct copy.
- Start transactions only when necessary, not after every commit().
- Release the GIL while making a connection (as suggested by Peter
  Schuller).
- If available, use decimal.Decimal for numeric types.
- Allow DB wrapper to be used with DB-API 2 connections (as
  suggested by Chris Hilton).
- Made private attributes of DB wrapper accessible.
- Dropped dependence on mx.DateTime module.
- Support for PQescapeStringConn() and PQescapeByteaConn(); these
  are now also used by the internal _quote() functions.
- Added 'int8' to INTEGER types. New SMALLINT type.
- Added a way to find the number of rows affected by a query()
  with the classic pg module by returning it as a string. For single
  inserts, query() still returns the oid as an integer. The pgdb
  module already provides the "rowcount" cursor attribute for the
  same purpose.
- Improved getnotify() by calling PQconsumeInput() instead of
  submitting an empty command.
- Removed compatibility code for old OID munging style.
- The insert() and update() methods now use the "returning" clause
  if possible to get all changed values, and they also check in
  advance whether a subsequent select is possible, so that ongoing
  transactions won't break if there is no select privilege.
- Added "protocol_version" and "server_version" attributes.
- Revived the "user" attribute.
- The pg module now works correctly with composite primary keys;
  these are represented as frozensets.
- Removed the undocumented and actually unnecessary "view"
  parameter from the get() method.
- get() raises a nicer ProgrammingError instead of a KeyError if
  no primary key was found.
- delete() now also works based on the primary key if no oid
  available and returns whether the row existed or not.</changelog>
  <changelog author="jengelh@medozas.de" date="1316260800">- Remove redundant tags/sections from specfile</changelog>
  <changelog author="p.drouand@gmail.com" date="1418472000">- Clean up specfile
- Use download Url as source
- Update to version 4.1.1
  + Add WhenNotified class and method.  Replaces need for third party
    pgnotify.
  + Sharpen test for inserting current_timestamp.
  + Add more quote tests.  False and 0 should evaluate to NULL.
  + More tests   + Any number other than 0 is True.
  + Do not use positional parameters internally.
    This restores backward compatibility with version 4.0.
  + Add methods for changing the decimal point.
- Changes from version 4.1
  + Dropped support for Python below 2.5 and PostgreSQL below 8.3.
  + Added support for Python up to 2.7 and PostgreSQL up to 9.2.
  + Particularly, support PQescapeLiteral() and PQescapeIdentifier().
  + The query method of the classic API now supports positional parameters.
    This an effective way to pass arbitrary or unknown data without worrying
    about SQL injection or syntax errors
  + The classic API now supports a method namedresult() in addition to
    getresult() and dictresult(), which returns the rows of the result
    as named tuples if these are supported (Python 2.6 or higher).
  + The classic API has got the new methods begin(), commit(), rollback(),
    savepoint() and release() for handling transactions.
  + Both classic and DBAPI 2 connections can now be used as context
    managers for encapsulating transactions.
  + The execute() and executemany() methods now return the cursor object,
    so you can now write statements like "for row in cursor.execute(...)"
  + Binary objects are now automatically escaped and unescaped.
  + Bug in money quoting fixed.  Amounts of $0.00 handled correctly.
  + Proper handling of date and time objects as input.
  + Proper handling of floats with 'nan' or 'inf' values as input.
  + Fixed the set_decimal() function.
  + All DatabaseError instances now have a sqlstate attribute.
  + The getnotify() method can now also return payload strings (#15).
  + Better support for notice processing with the new methods
    set_notice_receiver() and get_notice_receiver()
  + Open transactions are rolled back when pgdb connections are closed
  + Connections and cursors can now be used with the "with" statement
  + New method use_regtypes() that can be called to let getattnames()
  return regular type names instead of the simplified classic types (#44).
- Fix Provides/Obsoletes tags</changelog>
</package>
<package pkgid="cdfb6ff142c9b8cedb41a3d57b0fca71c506d159d8f85d05d85c5b180c9aa51e" name="barman" arch="noarch">
  <version epoch="0" ver="2.1" rel="1.1"/>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1323172800">- Initial packaging.</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1336564800">- Update to version 0.99.0</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1337083200">- Add cron job</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1337256000">- Fixed documentation</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1341576000">- Open source release</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1350043200">- New release 1.1.0
- Some improvements from Devrim Gunduz &lt;devrim@gunduz.org&gt;</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1350388800">- New release 1.1.1</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1354190400">- New release 1.1.2</changelog>
  <changelog author="darin@darins.net" date="1358251200">- Update and cleanup .spec for OpenSUSE
- Moved %changlog to .changes</changelog>
  <changelog author="darin@darins.net" date="1362571200">- Update to 1.2.0
- fix group</changelog>
  <changelog author="darin@darins.net" date="1362657600">- comment require python-abi
- require python-argh &gt;=0.21.2</changelog>
  <changelog author="boris@steki.net" date="1380888000">- updated to latest upstream 1.2.3
  - Added support for PostgreSQL 9.3
  - Added support for the "--target-name" recovery option,
    which allows to restore to a named point previously
    specified with pg_create_restore_point
    (only for PostgreSQL 9.1 and above users)
  - Fix python 2.6 compatibility
  - Added the "bandwidth_limit" global/server option which allows
    to limit the I/O bandwidth (in KBPS)
    for backup and recovery operations</changelog>
  <changelog author="boris@steki.net" date="1391515200">- updated to latest upstream version 1.3.0
  * Refactored BackupInfo class for backup
    metadata to use the new FieldListFile class (infofile module)
  * Refactored output layer to use a dedicated module, in order to
    facilitate integration with Nagios (NagiosOutputWriter class)
  * Refactored subprocess handling in order to isolate stdin/stderr/
    stdout channels (command_wrappers module)
  * Refactored hook scripts management
  * Extracted logging configuration and userid
    enforcement from the configuration class.
  * Support for hook scripts to be executed before and after
    a WAL file is archived, through the 'pre_archive_script'
    and 'post_archive_script' configuration options.
  * Implemented immediate checkpoint capability with
  - -immediate-checkpoint command option and 'immediate_checkpoint'
    configuration option
  * Implemented network compression for remote backup and recovery
    through the 'network_compression' configuration option (#19)
  * Implemented the 'rebuild-xlogdb' command (Closes #27 and #28)
  * Added deduplication of tablespaces located inside the PGDATA directory
  * Refactored remote recovery code to work the same way local recovery
    does, by performing remote directory preparation (assuming
    the remote user has the right permissions on the remote server)
  * 'barman backup' now tries and create server directories before
    attempting to execute a full backup (#14)
  * Fixed bug #22: improved documentation for tablespaces relocation
  * Fixed bug #31: 'barman cron' checks directory permissions for lock file
  * Fixed bug #32: xlog.db read access during cron activities</changelog>
  <changelog author="boris@steki.net" date="1410177600">- updated to latest upstream version 1.3.3
  + most notable changes are:
  - refactored building of full path of a WAL file
  - Estimates WAL production rate for a backup
  - Really fix "ssh" version detection in "barman diagnose" command
  - Add command line options for retry of backup/recover copy
  - Implemented the --retry-times (including --no-retry) and --retry-sleep
  - Display compression ratio for WALs in show-backup
  - Support for 'last_backup_max_age'
    This new global/server option allows administrators
    to set the max age of the last backup, making it easier
    to detect any issues with periodical backup execution.
  - Support for "smart" incremental recovery
    Avoid invoking rsync with --checksum option during recovery
  - Use Postgres' server time for both begin_time and end_time
  - Retry option for base backup
    If a network error happens during rsync, add the ability
    to retry a defined number of time.
- for verbose changelog please read changes info in
  /usr/share/doc/packages/barman/ChangeLog</changelog>
  <changelog author="mrueckert@suse.de" date="1433937600">- update to 1.4.1
  - Fix for WAL archival stop working if first backup is EMPTY
    (Closes: #64)
  - Fix exception during error handling in Barman recovery (Closes:
    [#] 65)
  - After a backup, limit cron activity to WAL archiving only
    (Closes: #62)
  - Improved robustness and error reporting of the backup delete
    command (Closes: #63)
  - Fix computation of WAL production ratio as reported in the
    show-backup command
  - Improved management of xlogb file, which is now correctly
    fsynced when updated. Also, the rebuild-xlogdb command now
    operates on a temporary new file, which overwrites the main one
    when finished.
  - Add unit tests for dateutil module compatibility
  - Modified Barman version following PEP 440 rules and added
    support of tests in Python 3.4
- changes from 1.4.0
  - Incremental base backup implementation through the reuse_backup
    global/server option. Possible values are off (disabled,
    default), copy (preventing unmodified files from being
    transferred) and link (allowing for deduplication through hard
    links).
  - Store and show deduplication effects when using reuse_backup=
    link.
  - Added transparent support of pg_stat_archiver (PostgreSQL 9.4)
    in check, show-server and status commands.
  - Improved administration by invoking WAL maintenance at the end
    of a successful backup.
  - Changed the way unused WAL files are trashed, by
    differentiating between concurrent and exclusive backup cases.
  - Improved performance of WAL statistics calculation.
  - Treat a missing pg_ident.conf as a WARNING rather than an
    error.
  - Refactored output layer by removing remaining yield calls.
  - Check that rsync is in the system path.
  - Include history files in WAL management.
  - Improved robustness through more unit tests.
  - Fixed bug #55: Ignore fsync EINVAL errors on directories.
  - Fixed bug #58: retention policies delete.
- unified tabs and spaces to spaces in the spec file
- added barman-tutorial.en.pdf to the documentation
- dont use sles_version for the noarch conditional. suse_version &gt;
  1110 is better.
- python-argcomplete requires didnt use the __python_ver macro
  got noticed when i tried to build it with python 3
- documentation says we need dateutils &lt; 2 as &gt;= 2.0 requires
  python3. Encode that also in the requires
- add requires for rsync as specified in the docs</changelog>
  <changelog author="mrueckert@suse.de" date="1433937601">- relax the dateutils requires again</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- update to 1.6.0
  - Support for streaming replication connection through the
    streaming_conninfo server option
  - Support for the streaming_archiver option that allows Barman to
    receive WAL files through PostgreSQL's native streaming
    protocol.  When set to 'on', it relies on pg_receivexlog to
    receive WAL data, reducing Recovery Point Objective. Currently,
    WAL streaming is an additional feature (standard log archiving
    is still required)
  - Implement the receive-wal command that, when streaming_archiver
    is on, wraps pg_receivexlog for WAL streaming. Add --stop
    option to stop receiving WAL files via streaming protocol. Add
  - -reset option to reset the streaming status and restart from
    the current xlog in Postgres.
  - Automatic management (startup and stop) of receive-wal command
    via cron command
  - Support for the path_prefix configuration option
  - Introduction of the archiver option (currently fixed to on)
    which enables continuous WAL archiving for a specific server,
    through log shipping via PostgreSQL's archive_command
  - Support for streaming_wals_directory and errors_directory
    options
  - Management of WAL duplicates in archive-wal command and
    integration with check command
  - Verify if pg_receivexlog is running in check command when
    streaming_archiver is enabled
  - Verify if failed backups are present in check command
  - Accept compressed WAL files in incoming directory
  - Add support for the pigz compressor (thanks to Stefano
    Zacchiroli zack@upsilon.cc)
  - Implement pygzip and pybzip2 compressors (based on an initial
    idea of Christoph Moench-Tegeder christoph@2ndquadrant.de)
  - Creation of an implicit restore point at the end of a backup
  - Current size of the PostgreSQL data files in barman status
  - Permit archive_mode=always for PostgreSQL 9.5 servers (thanks
    to Christoph Moench-Tegeder christoph@2ndquadrant.de)
  - Complete refactoring of the code responsible for connecting to
    PostgreSQL
  - Improve messaging of cron command regarding sub-processes
  - Native support for Python &gt;= 3.3
  - Changes of behaviour:
  - Stop trashing WAL files during archive-wal (commit:e3a1d16)
  - Bug fixes:
  - Atomic WAL file archiving (#9 and #12)
  - Propagate "-c" option to any Barman subprocess (#19)
  - Fix management of backup ID during backup deletion (#22)
  - Improve archive-wal robustness and log messages (#24)
  - Improve error handling in case of missing parameters</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 2.0:
  - Support for pg_basebackup and base backups over the PostgreSQL
    streaming replication protocol with backup_method=postgres
    (PostgreSQL 9.1 or higher required)
  - Support for physical replication slots through the slot_name
    configuration option as well as the --create-slot and
  - -drop-slot options for the receive-wal command (PostgreSQL 9.4
    or higher required). When slot_name is specified and
    streaming_archiver is enabled, receive-wal transparently
    integrates with pg_receivexlog, and check makes sure that slots
    exist and are actively used
  - Support for the new backup API introduced in PostgreSQL 9.6,
    which transparently enables concurrent backups and backups from
    standby servers using the standard rsync method of backup.
    Concurrent backup was only possible for PostgreSQL 9.2 to 9.5
    versions through the pgespresso extension. The new backup API
    will make pgespresso redundant in the future
  - If properly configured, Barman can function as a synchronous
    standby in terms of WAL streaming. By properly setting the
    streaming_archiver_name in the synchronous_standby_names
    priority list on the master, and enabling replication slot
    support, the receive-wal command can now be part of a
    PostgreSQL synchronous replication cluster, bringing RPO=0
    (PostgreSQL 9.5.5 or higher required)
  - Introduce barman-wal-restore, a standard and robust script
    written in Python that can be used as restore_command in
    recovery.conf files of any standby server of a cluster. It
    supports remote parallel fetching of WAL files by efficiently
    invoking get-wal through SSH.  Currently available as a
    separate project called barman-cli. The barman-cli package is
    required for remote recovery when get-wal is listed in
    recovery_options
  - Control the maximum execution time of the check command through
    the check_timeout global/server configuration option (30
    seconds by default)
  - Limit the number of WAL segments that are processed by an
    archive-wal run, through the archiver_batch_size and
    streaming_archiver_batch_size global/server options which
    control archiving of WAL segments coming from, respectively,
    the standard archiver and receive-wal
  - Removed locking of the XLOG database during check operations
  - The show-backup command is now aware of timelines and properly
    displays which timelines can be used as recovery targets for a
    given base backup. Internally, Barman is now capable of parsing
    .history files
  - Improved the logic behind the retry mechanism when copy
    operations experience problems. This involves backup (rsync and
    postgres) as well as remote recovery (rsync)
  - Code refactoring involving remote command and physical copy
    interfaces
  - Bug fixes:
  - Correctly handle .history files from streaming
  - Fix replication-status on PostgreSQL 9.1
  - Fix replication-status when sent and write locations are not
    available
  - Fix misleading message on pg_receivexlog termination
- replace tutorial.pdf with manual.pdf</changelog>
  <changelog author="bo@suse.de" date="1486468800">- update to 2.1:
  - Add --archive and --archive-timeout options to switch-xlog command
  - Preliminary support for PostgreSQL 10 (#73)
  - Minor additions:
  - Add last archived WAL info to diagnose output
  - Add start time and execution time to the output of delete command
  - Minor bug fixes:
  - Return failure for get-wal command on inactive server
  - Make streaming_archiver_names and streaming_backup_name options
    global (#57)
  - Fix rsync failures due to files truncated during transfer (#64)
  - Correctly handle compressed history files (#66)
  - Avoid de-referencing symlinks in pg_tblspc when preparing
    recovery (#55)
  - Fix comparison of last archiving failure (#40, #58)
  - Avoid failing recovery if postgresql.conf is not writable (#68)
  - Fix output of replication-status command (#56)
  - Exclude files from backups like pg_basebackup (#65, #72)
  - Exclude directories from other Postgres versions while copying
    tablespaces (#74)
  - Make retry hook script options global
- updated manual to 2.1 version</changelog>
</package>
<package pkgid="33ce1bd9d743bedecdba3fb4ca14ab676154eed00eaa9a3bf2ab02b24843341d" name="barman" arch="src">
  <version epoch="0" ver="2.1" rel="1.1"/>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1323172800">- Initial packaging.</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1336564800">- Update to version 0.99.0</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1337083200">- Add cron job</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1337256000">- Fixed documentation</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1341576000">- Open source release</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1350043200">- New release 1.1.0
- Some improvements from Devrim Gunduz &lt;devrim@gunduz.org&gt;</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1350388800">- New release 1.1.1</changelog>
  <changelog author="marco.nenciarini@2ndquadrant.it" date="1354190400">- New release 1.1.2</changelog>
  <changelog author="darin@darins.net" date="1358251200">- Update and cleanup .spec for OpenSUSE
- Moved %changlog to .changes</changelog>
  <changelog author="darin@darins.net" date="1362571200">- Update to 1.2.0
- fix group</changelog>
  <changelog author="darin@darins.net" date="1362657600">- comment require python-abi
- require python-argh &gt;=0.21.2</changelog>
  <changelog author="boris@steki.net" date="1380888000">- updated to latest upstream 1.2.3
  - Added support for PostgreSQL 9.3
  - Added support for the "--target-name" recovery option,
    which allows to restore to a named point previously
    specified with pg_create_restore_point
    (only for PostgreSQL 9.1 and above users)
  - Fix python 2.6 compatibility
  - Added the "bandwidth_limit" global/server option which allows
    to limit the I/O bandwidth (in KBPS)
    for backup and recovery operations</changelog>
  <changelog author="boris@steki.net" date="1391515200">- updated to latest upstream version 1.3.0
  * Refactored BackupInfo class for backup
    metadata to use the new FieldListFile class (infofile module)
  * Refactored output layer to use a dedicated module, in order to
    facilitate integration with Nagios (NagiosOutputWriter class)
  * Refactored subprocess handling in order to isolate stdin/stderr/
    stdout channels (command_wrappers module)
  * Refactored hook scripts management
  * Extracted logging configuration and userid
    enforcement from the configuration class.
  * Support for hook scripts to be executed before and after
    a WAL file is archived, through the 'pre_archive_script'
    and 'post_archive_script' configuration options.
  * Implemented immediate checkpoint capability with
  - -immediate-checkpoint command option and 'immediate_checkpoint'
    configuration option
  * Implemented network compression for remote backup and recovery
    through the 'network_compression' configuration option (#19)
  * Implemented the 'rebuild-xlogdb' command (Closes #27 and #28)
  * Added deduplication of tablespaces located inside the PGDATA directory
  * Refactored remote recovery code to work the same way local recovery
    does, by performing remote directory preparation (assuming
    the remote user has the right permissions on the remote server)
  * 'barman backup' now tries and create server directories before
    attempting to execute a full backup (#14)
  * Fixed bug #22: improved documentation for tablespaces relocation
  * Fixed bug #31: 'barman cron' checks directory permissions for lock file
  * Fixed bug #32: xlog.db read access during cron activities</changelog>
  <changelog author="boris@steki.net" date="1410177600">- updated to latest upstream version 1.3.3
  + most notable changes are:
  - refactored building of full path of a WAL file
  - Estimates WAL production rate for a backup
  - Really fix "ssh" version detection in "barman diagnose" command
  - Add command line options for retry of backup/recover copy
  - Implemented the --retry-times (including --no-retry) and --retry-sleep
  - Display compression ratio for WALs in show-backup
  - Support for 'last_backup_max_age'
    This new global/server option allows administrators
    to set the max age of the last backup, making it easier
    to detect any issues with periodical backup execution.
  - Support for "smart" incremental recovery
    Avoid invoking rsync with --checksum option during recovery
  - Use Postgres' server time for both begin_time and end_time
  - Retry option for base backup
    If a network error happens during rsync, add the ability
    to retry a defined number of time.
- for verbose changelog please read changes info in
  /usr/share/doc/packages/barman/ChangeLog</changelog>
  <changelog author="mrueckert@suse.de" date="1433937600">- update to 1.4.1
  - Fix for WAL archival stop working if first backup is EMPTY
    (Closes: #64)
  - Fix exception during error handling in Barman recovery (Closes:
    [#] 65)
  - After a backup, limit cron activity to WAL archiving only
    (Closes: #62)
  - Improved robustness and error reporting of the backup delete
    command (Closes: #63)
  - Fix computation of WAL production ratio as reported in the
    show-backup command
  - Improved management of xlogb file, which is now correctly
    fsynced when updated. Also, the rebuild-xlogdb command now
    operates on a temporary new file, which overwrites the main one
    when finished.
  - Add unit tests for dateutil module compatibility
  - Modified Barman version following PEP 440 rules and added
    support of tests in Python 3.4
- changes from 1.4.0
  - Incremental base backup implementation through the reuse_backup
    global/server option. Possible values are off (disabled,
    default), copy (preventing unmodified files from being
    transferred) and link (allowing for deduplication through hard
    links).
  - Store and show deduplication effects when using reuse_backup=
    link.
  - Added transparent support of pg_stat_archiver (PostgreSQL 9.4)
    in check, show-server and status commands.
  - Improved administration by invoking WAL maintenance at the end
    of a successful backup.
  - Changed the way unused WAL files are trashed, by
    differentiating between concurrent and exclusive backup cases.
  - Improved performance of WAL statistics calculation.
  - Treat a missing pg_ident.conf as a WARNING rather than an
    error.
  - Refactored output layer by removing remaining yield calls.
  - Check that rsync is in the system path.
  - Include history files in WAL management.
  - Improved robustness through more unit tests.
  - Fixed bug #55: Ignore fsync EINVAL errors on directories.
  - Fixed bug #58: retention policies delete.
- unified tabs and spaces to spaces in the spec file
- added barman-tutorial.en.pdf to the documentation
- dont use sles_version for the noarch conditional. suse_version &gt;
  1110 is better.
- python-argcomplete requires didnt use the __python_ver macro
  got noticed when i tried to build it with python 3
- documentation says we need dateutils &lt; 2 as &gt;= 2.0 requires
  python3. Encode that also in the requires
- add requires for rsync as specified in the docs</changelog>
  <changelog author="mrueckert@suse.de" date="1433937601">- relax the dateutils requires again</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- update to 1.6.0
  - Support for streaming replication connection through the
    streaming_conninfo server option
  - Support for the streaming_archiver option that allows Barman to
    receive WAL files through PostgreSQL's native streaming
    protocol.  When set to 'on', it relies on pg_receivexlog to
    receive WAL data, reducing Recovery Point Objective. Currently,
    WAL streaming is an additional feature (standard log archiving
    is still required)
  - Implement the receive-wal command that, when streaming_archiver
    is on, wraps pg_receivexlog for WAL streaming. Add --stop
    option to stop receiving WAL files via streaming protocol. Add
  - -reset option to reset the streaming status and restart from
    the current xlog in Postgres.
  - Automatic management (startup and stop) of receive-wal command
    via cron command
  - Support for the path_prefix configuration option
  - Introduction of the archiver option (currently fixed to on)
    which enables continuous WAL archiving for a specific server,
    through log shipping via PostgreSQL's archive_command
  - Support for streaming_wals_directory and errors_directory
    options
  - Management of WAL duplicates in archive-wal command and
    integration with check command
  - Verify if pg_receivexlog is running in check command when
    streaming_archiver is enabled
  - Verify if failed backups are present in check command
  - Accept compressed WAL files in incoming directory
  - Add support for the pigz compressor (thanks to Stefano
    Zacchiroli zack@upsilon.cc)
  - Implement pygzip and pybzip2 compressors (based on an initial
    idea of Christoph Moench-Tegeder christoph@2ndquadrant.de)
  - Creation of an implicit restore point at the end of a backup
  - Current size of the PostgreSQL data files in barman status
  - Permit archive_mode=always for PostgreSQL 9.5 servers (thanks
    to Christoph Moench-Tegeder christoph@2ndquadrant.de)
  - Complete refactoring of the code responsible for connecting to
    PostgreSQL
  - Improve messaging of cron command regarding sub-processes
  - Native support for Python &gt;= 3.3
  - Changes of behaviour:
  - Stop trashing WAL files during archive-wal (commit:e3a1d16)
  - Bug fixes:
  - Atomic WAL file archiving (#9 and #12)
  - Propagate "-c" option to any Barman subprocess (#19)
  - Fix management of backup ID during backup deletion (#22)
  - Improve archive-wal robustness and log messages (#24)
  - Improve error handling in case of missing parameters</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 2.0:
  - Support for pg_basebackup and base backups over the PostgreSQL
    streaming replication protocol with backup_method=postgres
    (PostgreSQL 9.1 or higher required)
  - Support for physical replication slots through the slot_name
    configuration option as well as the --create-slot and
  - -drop-slot options for the receive-wal command (PostgreSQL 9.4
    or higher required). When slot_name is specified and
    streaming_archiver is enabled, receive-wal transparently
    integrates with pg_receivexlog, and check makes sure that slots
    exist and are actively used
  - Support for the new backup API introduced in PostgreSQL 9.6,
    which transparently enables concurrent backups and backups from
    standby servers using the standard rsync method of backup.
    Concurrent backup was only possible for PostgreSQL 9.2 to 9.5
    versions through the pgespresso extension. The new backup API
    will make pgespresso redundant in the future
  - If properly configured, Barman can function as a synchronous
    standby in terms of WAL streaming. By properly setting the
    streaming_archiver_name in the synchronous_standby_names
    priority list on the master, and enabling replication slot
    support, the receive-wal command can now be part of a
    PostgreSQL synchronous replication cluster, bringing RPO=0
    (PostgreSQL 9.5.5 or higher required)
  - Introduce barman-wal-restore, a standard and robust script
    written in Python that can be used as restore_command in
    recovery.conf files of any standby server of a cluster. It
    supports remote parallel fetching of WAL files by efficiently
    invoking get-wal through SSH.  Currently available as a
    separate project called barman-cli. The barman-cli package is
    required for remote recovery when get-wal is listed in
    recovery_options
  - Control the maximum execution time of the check command through
    the check_timeout global/server configuration option (30
    seconds by default)
  - Limit the number of WAL segments that are processed by an
    archive-wal run, through the archiver_batch_size and
    streaming_archiver_batch_size global/server options which
    control archiving of WAL segments coming from, respectively,
    the standard archiver and receive-wal
  - Removed locking of the XLOG database during check operations
  - The show-backup command is now aware of timelines and properly
    displays which timelines can be used as recovery targets for a
    given base backup. Internally, Barman is now capable of parsing
    .history files
  - Improved the logic behind the retry mechanism when copy
    operations experience problems. This involves backup (rsync and
    postgres) as well as remote recovery (rsync)
  - Code refactoring involving remote command and physical copy
    interfaces
  - Bug fixes:
  - Correctly handle .history files from streaming
  - Fix replication-status on PostgreSQL 9.1
  - Fix replication-status when sent and write locations are not
    available
  - Fix misleading message on pg_receivexlog termination
- replace tutorial.pdf with manual.pdf</changelog>
  <changelog author="bo@suse.de" date="1486468800">- update to 2.1:
  - Add --archive and --archive-timeout options to switch-xlog command
  - Preliminary support for PostgreSQL 10 (#73)
  - Minor additions:
  - Add last archived WAL info to diagnose output
  - Add start time and execution time to the output of delete command
  - Minor bug fixes:
  - Return failure for get-wal command on inactive server
  - Make streaming_archiver_names and streaming_backup_name options
    global (#57)
  - Fix rsync failures due to files truncated during transfer (#64)
  - Correctly handle compressed history files (#66)
  - Avoid de-referencing symlinks in pg_tblspc when preparing
    recovery (#55)
  - Fix comparison of last archiving failure (#40, #58)
  - Avoid failing recovery if postgresql.conf is not writable (#68)
  - Fix output of replication-status command (#56)
  - Exclude files from backups like pg_basebackup (#65, #72)
  - Exclude directories from other Postgres versions while copying
    tablespaces (#74)
  - Make retry hook script options global
- updated manual to 2.1 version</changelog>
</package>
<package pkgid="a441d3bc83af7bf4ce74510abc2aa7e278a7c24fab3724b2e8cd309508f6635c" name="libecpg6" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="10.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="7a7cf6b4fe7bb8e12142988116630c35ec3a34788a063942bac5482cb0a74c86" name="libecpg6-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="10.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="51677bcc85404c1e04a9c5a5753ef7f99133672ea09c963a98f97b3e3713e684" name="libpcp1" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="3bcf0fe54b49a88348f0fd1e20fe15836e1861ee1d8e5e61d80f7bb502c0c0f0" name="libpcp1-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="3ff1b7f579f82a07eb66f1092271864341af5448d4f4a3d6077e5248daa9c84c" name="libpgeasy" arch="src">
  <version epoch="0" ver="3.0.4" rel="209.2"/>
  <changelog author="max@suse.de" date="1043668800">- Split off from the postgresql-libs package, because they are now
  separate projects.</changelog>
  <changelog author="max@suse.de" date="1043668801">- Quote $RPM_OPT_FLAGS.
- Added split-provides.</changelog>
  <changelog author="max@suse.de" date="1092916800">- New version: 3.0.4.
- Renamed from pgeasy to libpgeasy.</changelog>
  <changelog author="ro@suse.de" date="1100174400">- fixed file list</changelog>
  <changelog author="ro@suse.de" date="1100779200">- use kerberos-devel-packages</changelog>
  <changelog author="dmueller@suse.de" date="1130932800">- don't build as root</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="crrodriguez@suse.de" date="1198756800">- fix library-without-ldconfig-post* errors</changelog>
  <changelog author="mpluskal@suse.com" date="1448020800">- Cleanup spec file with spec-cleaner
- Split devel package and library
- Remove old provides
- Do not ship .la file</changelog>
</package>
<package pkgid="770d8c0d05380186bc36af0a9964a645a60b7176734db1dffce12546f3dd95bf" name="libpgeasy-debugsource" arch="x86_64">
  <version epoch="0" ver="3.0.4" rel="209.2"/>
  <changelog author="max@suse.de" date="1043668800">- Split off from the postgresql-libs package, because they are now
  separate projects.</changelog>
  <changelog author="max@suse.de" date="1043668801">- Quote $RPM_OPT_FLAGS.
- Added split-provides.</changelog>
  <changelog author="max@suse.de" date="1092916800">- New version: 3.0.4.
- Renamed from pgeasy to libpgeasy.</changelog>
  <changelog author="ro@suse.de" date="1100174400">- fixed file list</changelog>
  <changelog author="ro@suse.de" date="1100779200">- use kerberos-devel-packages</changelog>
  <changelog author="dmueller@suse.de" date="1130932800">- don't build as root</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="crrodriguez@suse.de" date="1198756800">- fix library-without-ldconfig-post* errors</changelog>
  <changelog author="mpluskal@suse.com" date="1448020800">- Cleanup spec file with spec-cleaner
- Split devel package and library
- Remove old provides
- Do not ship .la file</changelog>
</package>
<package pkgid="149d16c3e09847dc81b41817434028931e4e05034ba7a155ef7b53c51c476fdc" name="libpgeasy-devel" arch="x86_64">
  <version epoch="0" ver="3.0.4" rel="209.2"/>
  <changelog author="max@suse.de" date="1043668800">- Split off from the postgresql-libs package, because they are now
  separate projects.</changelog>
  <changelog author="max@suse.de" date="1043668801">- Quote $RPM_OPT_FLAGS.
- Added split-provides.</changelog>
  <changelog author="max@suse.de" date="1092916800">- New version: 3.0.4.
- Renamed from pgeasy to libpgeasy.</changelog>
  <changelog author="ro@suse.de" date="1100174400">- fixed file list</changelog>
  <changelog author="ro@suse.de" date="1100779200">- use kerberos-devel-packages</changelog>
  <changelog author="dmueller@suse.de" date="1130932800">- don't build as root</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="crrodriguez@suse.de" date="1198756800">- fix library-without-ldconfig-post* errors</changelog>
  <changelog author="mpluskal@suse.com" date="1448020800">- Cleanup spec file with spec-cleaner
- Split devel package and library
- Remove old provides
- Do not ship .la file</changelog>
</package>
<package pkgid="cf4cf8b0a6948f9a845f979179ab39e6d4f0729fd9ae5e4649992e55c2ccb93f" name="libpgeasy3" arch="x86_64">
  <version epoch="0" ver="3.0.4" rel="209.2"/>
  <changelog author="max@suse.de" date="1043668800">- Split off from the postgresql-libs package, because they are now
  separate projects.</changelog>
  <changelog author="max@suse.de" date="1043668801">- Quote $RPM_OPT_FLAGS.
- Added split-provides.</changelog>
  <changelog author="max@suse.de" date="1092916800">- New version: 3.0.4.
- Renamed from pgeasy to libpgeasy.</changelog>
  <changelog author="ro@suse.de" date="1100174400">- fixed file list</changelog>
  <changelog author="ro@suse.de" date="1100779200">- use kerberos-devel-packages</changelog>
  <changelog author="dmueller@suse.de" date="1130932800">- don't build as root</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="crrodriguez@suse.de" date="1198756800">- fix library-without-ldconfig-post* errors</changelog>
  <changelog author="mpluskal@suse.com" date="1448020800">- Cleanup spec file with spec-cleaner
- Split devel package and library
- Remove old provides
- Do not ship .la file</changelog>
</package>
<package pkgid="2b05123ad3806c04839302f4f1e3344967dfc3558467d19f5a36ff275a65e736" name="libpgeasy3-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.0.4" rel="209.2"/>
  <changelog author="max@suse.de" date="1043668800">- Split off from the postgresql-libs package, because they are now
  separate projects.</changelog>
  <changelog author="max@suse.de" date="1043668801">- Quote $RPM_OPT_FLAGS.
- Added split-provides.</changelog>
  <changelog author="max@suse.de" date="1092916800">- New version: 3.0.4.
- Renamed from pgeasy to libpgeasy.</changelog>
  <changelog author="ro@suse.de" date="1100174400">- fixed file list</changelog>
  <changelog author="ro@suse.de" date="1100779200">- use kerberos-devel-packages</changelog>
  <changelog author="dmueller@suse.de" date="1130932800">- don't build as root</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="crrodriguez@suse.de" date="1198756800">- fix library-without-ldconfig-post* errors</changelog>
  <changelog author="mpluskal@suse.com" date="1448020800">- Cleanup spec file with spec-cleaner
- Split devel package and library
- Remove old provides
- Do not ship .la file</changelog>
</package>
<package pkgid="6c2032882f2591fa162a8615b60f0e1420801b895f4c4be274d450beec481b1c" name="libpq5" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="10.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="c85e41565f98b3fdeb509ce6e9ef4a0b78d972bc59395e695c15336ffc78d1d0" name="libpq5-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="10.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="7b5338b8a62923eae2de9e4bd87cb31d1f6f39d3697b7428a05e206b3597e977" name="libpqxx" arch="src">
  <version epoch="0" ver="5.0.1" rel="40.2"/>
  <changelog author="ro@suse.de" date="1100779200">- use kerberos-devel-packages</changelog>
  <changelog author="max@suse.de" date="1136808000">- New version 2.5.5</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="max@suse.de" date="1185796800">- New version: 2.6.9 (#280593). Changes include:
  * Removed old 1.x API
  * Greatly reduced memory usage while escaping strings
  * Useful error messages when preparing statements
  * New cursor class, absolute_cursor
  * New, encoding-safe string-escaping functions
  * Radical rework of prepared statements;
    INCOMPATIBLE INTERFACE CHANGE!
  * Support for subtransactions
  * Detect more connection capabilities
  * Greatly improved cursor support
  * ... and many many mire bug fixes and improvements.
- Tell rpmlint to shut up.</changelog>
  <changelog author="aj@suse.de" date="1200312000">- Fix build with g++.</changelog>
  <changelog author="dmueller@suse.de" date="1200312001">- fix last change</changelog>
  <changelog author="schwab@suse.de" date="1214568000">- Use autoreconf.</changelog>
  <changelog author="crrodriguez@suse.de" date="1236945600">- remove static libraries</changelog>
  <changelog author="max@suse.de" date="1249300800">- New version: 3.0.1:
- All items marked as deprecated in the 2.x API have been removed.
- Fixed various problems in Visual C++ makefile for test suite.
- Fixed some problems with RPM packaging.
- Completely replaced cursor classes
- More helpful error messages on failed connections
- More detailed hierarchy of constraint-violation exception classes
- trigger is now called notify_listener, trigger header is now
  notify-listen
- New mixin base class pqxx_exception distinguishes libpqxx exception
  types
- Quoting is back! transaction_base::quote() &amp;
  connection_base::quote()
- Several build &amp; documentation problems with Visual C++ fixed
- Compile fixes for gcc 4.2, 4.3
- Uses strlcpy() where available, instead of strncpy()
- Keeps better track of applicable text encodings
- Fixed bug with prepared statement parameters in separate C++
  statements
- robusttransaction now works for multiple users
- Pipeline lets you cancel ongoing queries, e.g. because they run for
  too long
- Fixed broken escaping of binary values in tablewriter
- Floating-point types now represented with full precision
- Proper unit tests for new functionality
- New traits-based system for adding data types
- Floating-point infinities now supported
- Flushing/completing a pipeline now frees up the transaction for
  other use
- Completely reworked test suite, builds and runs much faster
- tablewriter supports writing of raw lines</changelog>
  <changelog author="max@suse.de" date="1266580800">- New version: 3.1:
- Shared libraries are now versioned by ABI: 3.1 instead of 3.1.0.
- Threading behaviour is now documented, and can be queried.
- Version information available at compile time.
- Supports parameterized statements.
- Result tuples now support slicing.
- Configure with --with-tr1=boost to use BOOST shared_ptr.
- String conversion now has its own header file.
- Supports read-only transactions.
- Uses shared_ptr if available.
- binarystring::str() is no longer cached; no longer returns
  reference.
- Lets you check whether a prepared statement has been defined.
- "Varargs" prepared statements.
- Unnamed prepared statements now supported.
- Results have iterator as well as const_iterator.
- Rewrite of robusttransaction logic; may actually do its job now.
- Connections support async query cancel from signal handler or
  thread.
- More documentation for performance features.</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- only use fdupes on 11.1 or newer</changelog>
  <changelog author="idonmez@novell.com" date="1306238400">- Add libpqxx-3.1-gcc46.patch, add missing cstddef include to
  fix compilation with gcc 4.6, upstream revision 1722</changelog>
  <changelog author="max@novell.com" date="1306324800">- Rename libpqxx-3.1-gcc46.patch to libpqxx-gcc46.patch.</changelog>
  <changelog author="aj@suse.de" date="1322913600">- Add require on pkg-config to provide pkg-config provides.
- Don't package libpqxx-3.1.so twice.</changelog>
  <changelog author="dimstar@opensuse.org" date="1332158400">- Add libpqxx-gcc47.patch: Fix build with gcc 4.7.</changelog>
  <changelog author="adam@mizerski.pl" date="1365508800">- update to 4.0.1
  * See NEWS or http://pqxx.org/development/libpqxx/browser/tags/4.0.1/NEWS
    for details.
- spec cleanup
  * Provide library in subpackage, which name follows
    shared library naming policy.
- removed libpqxx-rpmlintrc
  * it contained only addFilter("shlib-policy-name-error")
- removed patches libpqxx-gcc46.patch libpqxx-gcc47.patch -
  merged upstream.</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- add back buildroot to fix build on sle 11</changelog>
  <changelog author="dimstar@opensuse.org" date="1489492800">- Add libpqxx-sed-4.3.patch: Fix build with sed 4.3, which is
  stricter regarding [[:space:]] vs [:space:]. configure.ac needs
  this to be represented as [[[:space:]]], as autoFOO itself
  swallows one pair of [].
- Add libtool BuildRequires and call to autoreconf, as above patch
  touches the build system.</changelog>
  <changelog author="adam@mizerski.pl" date="1492430400">- update to 5.0.1
  * See NEWS or https://github.com/jtv/libpqxx/blob/5.0.1/NEWS
    for details
- rebased libpqxx-sed-4.3.patch
- split doc subpackage</changelog>
  <changelog author="jengelh@inai.de" date="1492948800">- Select better RPM groups</changelog>
</package>
<package pkgid="fb2b0e8e0aec2528c88172e34d62f883019c4d899d78a7ec88b72a9cdd42ad5f" name="libpqxx-5_0" arch="x86_64">
  <version epoch="0" ver="5.0.1" rel="40.2"/>
  <changelog author="crrodriguez@suse.de" date="1236945600">- remove static libraries</changelog>
  <changelog author="max@suse.de" date="1249300800">- New version: 3.0.1:
- All items marked as deprecated in the 2.x API have been removed.
- Fixed various problems in Visual C++ makefile for test suite.
- Fixed some problems with RPM packaging.
- Completely replaced cursor classes
- More helpful error messages on failed connections
- More detailed hierarchy of constraint-violation exception classes
- trigger is now called notify_listener, trigger header is now
  notify-listen
- New mixin base class pqxx_exception distinguishes libpqxx exception
  types
- Quoting is back! transaction_base::quote() &amp;
  connection_base::quote()
- Several build &amp; documentation problems with Visual C++ fixed
- Compile fixes for gcc 4.2, 4.3
- Uses strlcpy() where available, instead of strncpy()
- Keeps better track of applicable text encodings
- Fixed bug with prepared statement parameters in separate C++
  statements
- robusttransaction now works for multiple users
- Pipeline lets you cancel ongoing queries, e.g. because they run for
  too long
- Fixed broken escaping of binary values in tablewriter
- Floating-point types now represented with full precision
- Proper unit tests for new functionality
- New traits-based system for adding data types
- Floating-point infinities now supported
- Flushing/completing a pipeline now frees up the transaction for
  other use
- Completely reworked test suite, builds and runs much faster
- tablewriter supports writing of raw lines</changelog>
  <changelog author="max@suse.de" date="1266580800">- New version: 3.1:
- Shared libraries are now versioned by ABI: 3.1 instead of 3.1.0.
- Threading behaviour is now documented, and can be queried.
- Version information available at compile time.
- Supports parameterized statements.
- Result tuples now support slicing.
- Configure with --with-tr1=boost to use BOOST shared_ptr.
- String conversion now has its own header file.
- Supports read-only transactions.
- Uses shared_ptr if available.
- binarystring::str() is no longer cached; no longer returns
  reference.
- Lets you check whether a prepared statement has been defined.
- "Varargs" prepared statements.
- Unnamed prepared statements now supported.
- Results have iterator as well as const_iterator.
- Rewrite of robusttransaction logic; may actually do its job now.
- Connections support async query cancel from signal handler or
  thread.
- More documentation for performance features.</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- only use fdupes on 11.1 or newer</changelog>
  <changelog author="idonmez@novell.com" date="1306238400">- Add libpqxx-3.1-gcc46.patch, add missing cstddef include to
  fix compilation with gcc 4.6, upstream revision 1722</changelog>
  <changelog author="max@novell.com" date="1306324800">- Rename libpqxx-3.1-gcc46.patch to libpqxx-gcc46.patch.</changelog>
  <changelog author="aj@suse.de" date="1322913600">- Add require on pkg-config to provide pkg-config provides.
- Don't package libpqxx-3.1.so twice.</changelog>
  <changelog author="dimstar@opensuse.org" date="1332158400">- Add libpqxx-gcc47.patch: Fix build with gcc 4.7.</changelog>
  <changelog author="adam@mizerski.pl" date="1365508800">- update to 4.0.1
  * See NEWS or http://pqxx.org/development/libpqxx/browser/tags/4.0.1/NEWS
    for details.
- spec cleanup
  * Provide library in subpackage, which name follows
    shared library naming policy.
- removed libpqxx-rpmlintrc
  * it contained only addFilter("shlib-policy-name-error")
- removed patches libpqxx-gcc46.patch libpqxx-gcc47.patch -
  merged upstream.</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- add back buildroot to fix build on sle 11</changelog>
  <changelog author="dimstar@opensuse.org" date="1489492800">- Add libpqxx-sed-4.3.patch: Fix build with sed 4.3, which is
  stricter regarding [[:space:]] vs [:space:]. configure.ac needs
  this to be represented as [[[:space:]]], as autoFOO itself
  swallows one pair of [].
- Add libtool BuildRequires and call to autoreconf, as above patch
  touches the build system.</changelog>
  <changelog author="adam@mizerski.pl" date="1492430400">- update to 5.0.1
  * See NEWS or https://github.com/jtv/libpqxx/blob/5.0.1/NEWS
    for details
- rebased libpqxx-sed-4.3.patch
- split doc subpackage</changelog>
  <changelog author="jengelh@inai.de" date="1492948800">- Select better RPM groups</changelog>
</package>
<package pkgid="2e92c7ff9d6b2c5f47b1b814f51adf2ef3fcda5b1e6027ed7d7704721f845f72" name="libpqxx-5_0-debuginfo" arch="x86_64">
  <version epoch="0" ver="5.0.1" rel="40.2"/>
  <changelog author="crrodriguez@suse.de" date="1236945600">- remove static libraries</changelog>
  <changelog author="max@suse.de" date="1249300800">- New version: 3.0.1:
- All items marked as deprecated in the 2.x API have been removed.
- Fixed various problems in Visual C++ makefile for test suite.
- Fixed some problems with RPM packaging.
- Completely replaced cursor classes
- More helpful error messages on failed connections
- More detailed hierarchy of constraint-violation exception classes
- trigger is now called notify_listener, trigger header is now
  notify-listen
- New mixin base class pqxx_exception distinguishes libpqxx exception
  types
- Quoting is back! transaction_base::quote() &amp;
  connection_base::quote()
- Several build &amp; documentation problems with Visual C++ fixed
- Compile fixes for gcc 4.2, 4.3
- Uses strlcpy() where available, instead of strncpy()
- Keeps better track of applicable text encodings
- Fixed bug with prepared statement parameters in separate C++
  statements
- robusttransaction now works for multiple users
- Pipeline lets you cancel ongoing queries, e.g. because they run for
  too long
- Fixed broken escaping of binary values in tablewriter
- Floating-point types now represented with full precision
- Proper unit tests for new functionality
- New traits-based system for adding data types
- Floating-point infinities now supported
- Flushing/completing a pipeline now frees up the transaction for
  other use
- Completely reworked test suite, builds and runs much faster
- tablewriter supports writing of raw lines</changelog>
  <changelog author="max@suse.de" date="1266580800">- New version: 3.1:
- Shared libraries are now versioned by ABI: 3.1 instead of 3.1.0.
- Threading behaviour is now documented, and can be queried.
- Version information available at compile time.
- Supports parameterized statements.
- Result tuples now support slicing.
- Configure with --with-tr1=boost to use BOOST shared_ptr.
- String conversion now has its own header file.
- Supports read-only transactions.
- Uses shared_ptr if available.
- binarystring::str() is no longer cached; no longer returns
  reference.
- Lets you check whether a prepared statement has been defined.
- "Varargs" prepared statements.
- Unnamed prepared statements now supported.
- Results have iterator as well as const_iterator.
- Rewrite of robusttransaction logic; may actually do its job now.
- Connections support async query cancel from signal handler or
  thread.
- More documentation for performance features.</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- only use fdupes on 11.1 or newer</changelog>
  <changelog author="idonmez@novell.com" date="1306238400">- Add libpqxx-3.1-gcc46.patch, add missing cstddef include to
  fix compilation with gcc 4.6, upstream revision 1722</changelog>
  <changelog author="max@novell.com" date="1306324800">- Rename libpqxx-3.1-gcc46.patch to libpqxx-gcc46.patch.</changelog>
  <changelog author="aj@suse.de" date="1322913600">- Add require on pkg-config to provide pkg-config provides.
- Don't package libpqxx-3.1.so twice.</changelog>
  <changelog author="dimstar@opensuse.org" date="1332158400">- Add libpqxx-gcc47.patch: Fix build with gcc 4.7.</changelog>
  <changelog author="adam@mizerski.pl" date="1365508800">- update to 4.0.1
  * See NEWS or http://pqxx.org/development/libpqxx/browser/tags/4.0.1/NEWS
    for details.
- spec cleanup
  * Provide library in subpackage, which name follows
    shared library naming policy.
- removed libpqxx-rpmlintrc
  * it contained only addFilter("shlib-policy-name-error")
- removed patches libpqxx-gcc46.patch libpqxx-gcc47.patch -
  merged upstream.</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- add back buildroot to fix build on sle 11</changelog>
  <changelog author="dimstar@opensuse.org" date="1489492800">- Add libpqxx-sed-4.3.patch: Fix build with sed 4.3, which is
  stricter regarding [[:space:]] vs [:space:]. configure.ac needs
  this to be represented as [[[:space:]]], as autoFOO itself
  swallows one pair of [].
- Add libtool BuildRequires and call to autoreconf, as above patch
  touches the build system.</changelog>
  <changelog author="adam@mizerski.pl" date="1492430400">- update to 5.0.1
  * See NEWS or https://github.com/jtv/libpqxx/blob/5.0.1/NEWS
    for details
- rebased libpqxx-sed-4.3.patch
- split doc subpackage</changelog>
  <changelog author="jengelh@inai.de" date="1492948800">- Select better RPM groups</changelog>
</package>
<package pkgid="266bebd7c7af0fe7ed60fe7eefc4b22ea4213629236d100010e7373b4c6b6c97" name="libpqxx-debugsource" arch="x86_64">
  <version epoch="0" ver="5.0.1" rel="40.2"/>
  <changelog author="crrodriguez@suse.de" date="1236945600">- remove static libraries</changelog>
  <changelog author="max@suse.de" date="1249300800">- New version: 3.0.1:
- All items marked as deprecated in the 2.x API have been removed.
- Fixed various problems in Visual C++ makefile for test suite.
- Fixed some problems with RPM packaging.
- Completely replaced cursor classes
- More helpful error messages on failed connections
- More detailed hierarchy of constraint-violation exception classes
- trigger is now called notify_listener, trigger header is now
  notify-listen
- New mixin base class pqxx_exception distinguishes libpqxx exception
  types
- Quoting is back! transaction_base::quote() &amp;
  connection_base::quote()
- Several build &amp; documentation problems with Visual C++ fixed
- Compile fixes for gcc 4.2, 4.3
- Uses strlcpy() where available, instead of strncpy()
- Keeps better track of applicable text encodings
- Fixed bug with prepared statement parameters in separate C++
  statements
- robusttransaction now works for multiple users
- Pipeline lets you cancel ongoing queries, e.g. because they run for
  too long
- Fixed broken escaping of binary values in tablewriter
- Floating-point types now represented with full precision
- Proper unit tests for new functionality
- New traits-based system for adding data types
- Floating-point infinities now supported
- Flushing/completing a pipeline now frees up the transaction for
  other use
- Completely reworked test suite, builds and runs much faster
- tablewriter supports writing of raw lines</changelog>
  <changelog author="max@suse.de" date="1266580800">- New version: 3.1:
- Shared libraries are now versioned by ABI: 3.1 instead of 3.1.0.
- Threading behaviour is now documented, and can be queried.
- Version information available at compile time.
- Supports parameterized statements.
- Result tuples now support slicing.
- Configure with --with-tr1=boost to use BOOST shared_ptr.
- String conversion now has its own header file.
- Supports read-only transactions.
- Uses shared_ptr if available.
- binarystring::str() is no longer cached; no longer returns
  reference.
- Lets you check whether a prepared statement has been defined.
- "Varargs" prepared statements.
- Unnamed prepared statements now supported.
- Results have iterator as well as const_iterator.
- Rewrite of robusttransaction logic; may actually do its job now.
- Connections support async query cancel from signal handler or
  thread.
- More documentation for performance features.</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- only use fdupes on 11.1 or newer</changelog>
  <changelog author="idonmez@novell.com" date="1306238400">- Add libpqxx-3.1-gcc46.patch, add missing cstddef include to
  fix compilation with gcc 4.6, upstream revision 1722</changelog>
  <changelog author="max@novell.com" date="1306324800">- Rename libpqxx-3.1-gcc46.patch to libpqxx-gcc46.patch.</changelog>
  <changelog author="aj@suse.de" date="1322913600">- Add require on pkg-config to provide pkg-config provides.
- Don't package libpqxx-3.1.so twice.</changelog>
  <changelog author="dimstar@opensuse.org" date="1332158400">- Add libpqxx-gcc47.patch: Fix build with gcc 4.7.</changelog>
  <changelog author="adam@mizerski.pl" date="1365508800">- update to 4.0.1
  * See NEWS or http://pqxx.org/development/libpqxx/browser/tags/4.0.1/NEWS
    for details.
- spec cleanup
  * Provide library in subpackage, which name follows
    shared library naming policy.
- removed libpqxx-rpmlintrc
  * it contained only addFilter("shlib-policy-name-error")
- removed patches libpqxx-gcc46.patch libpqxx-gcc47.patch -
  merged upstream.</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- add back buildroot to fix build on sle 11</changelog>
  <changelog author="dimstar@opensuse.org" date="1489492800">- Add libpqxx-sed-4.3.patch: Fix build with sed 4.3, which is
  stricter regarding [[:space:]] vs [:space:]. configure.ac needs
  this to be represented as [[[:space:]]], as autoFOO itself
  swallows one pair of [].
- Add libtool BuildRequires and call to autoreconf, as above patch
  touches the build system.</changelog>
  <changelog author="adam@mizerski.pl" date="1492430400">- update to 5.0.1
  * See NEWS or https://github.com/jtv/libpqxx/blob/5.0.1/NEWS
    for details
- rebased libpqxx-sed-4.3.patch
- split doc subpackage</changelog>
  <changelog author="jengelh@inai.de" date="1492948800">- Select better RPM groups</changelog>
</package>
<package pkgid="2f750dc5af04ea21a2337608f664e03ae0b457ca38b36afc6870b1e6cddafd9d" name="libpqxx-devel" arch="x86_64">
  <version epoch="0" ver="5.0.1" rel="40.2"/>
  <changelog author="crrodriguez@suse.de" date="1236945600">- remove static libraries</changelog>
  <changelog author="max@suse.de" date="1249300800">- New version: 3.0.1:
- All items marked as deprecated in the 2.x API have been removed.
- Fixed various problems in Visual C++ makefile for test suite.
- Fixed some problems with RPM packaging.
- Completely replaced cursor classes
- More helpful error messages on failed connections
- More detailed hierarchy of constraint-violation exception classes
- trigger is now called notify_listener, trigger header is now
  notify-listen
- New mixin base class pqxx_exception distinguishes libpqxx exception
  types
- Quoting is back! transaction_base::quote() &amp;
  connection_base::quote()
- Several build &amp; documentation problems with Visual C++ fixed
- Compile fixes for gcc 4.2, 4.3
- Uses strlcpy() where available, instead of strncpy()
- Keeps better track of applicable text encodings
- Fixed bug with prepared statement parameters in separate C++
  statements
- robusttransaction now works for multiple users
- Pipeline lets you cancel ongoing queries, e.g. because they run for
  too long
- Fixed broken escaping of binary values in tablewriter
- Floating-point types now represented with full precision
- Proper unit tests for new functionality
- New traits-based system for adding data types
- Floating-point infinities now supported
- Flushing/completing a pipeline now frees up the transaction for
  other use
- Completely reworked test suite, builds and runs much faster
- tablewriter supports writing of raw lines</changelog>
  <changelog author="max@suse.de" date="1266580800">- New version: 3.1:
- Shared libraries are now versioned by ABI: 3.1 instead of 3.1.0.
- Threading behaviour is now documented, and can be queried.
- Version information available at compile time.
- Supports parameterized statements.
- Result tuples now support slicing.
- Configure with --with-tr1=boost to use BOOST shared_ptr.
- String conversion now has its own header file.
- Supports read-only transactions.
- Uses shared_ptr if available.
- binarystring::str() is no longer cached; no longer returns
  reference.
- Lets you check whether a prepared statement has been defined.
- "Varargs" prepared statements.
- Unnamed prepared statements now supported.
- Results have iterator as well as const_iterator.
- Rewrite of robusttransaction logic; may actually do its job now.
- Connections support async query cancel from signal handler or
  thread.
- More documentation for performance features.</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- only use fdupes on 11.1 or newer</changelog>
  <changelog author="idonmez@novell.com" date="1306238400">- Add libpqxx-3.1-gcc46.patch, add missing cstddef include to
  fix compilation with gcc 4.6, upstream revision 1722</changelog>
  <changelog author="max@novell.com" date="1306324800">- Rename libpqxx-3.1-gcc46.patch to libpqxx-gcc46.patch.</changelog>
  <changelog author="aj@suse.de" date="1322913600">- Add require on pkg-config to provide pkg-config provides.
- Don't package libpqxx-3.1.so twice.</changelog>
  <changelog author="dimstar@opensuse.org" date="1332158400">- Add libpqxx-gcc47.patch: Fix build with gcc 4.7.</changelog>
  <changelog author="adam@mizerski.pl" date="1365508800">- update to 4.0.1
  * See NEWS or http://pqxx.org/development/libpqxx/browser/tags/4.0.1/NEWS
    for details.
- spec cleanup
  * Provide library in subpackage, which name follows
    shared library naming policy.
- removed libpqxx-rpmlintrc
  * it contained only addFilter("shlib-policy-name-error")
- removed patches libpqxx-gcc46.patch libpqxx-gcc47.patch -
  merged upstream.</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- add back buildroot to fix build on sle 11</changelog>
  <changelog author="dimstar@opensuse.org" date="1489492800">- Add libpqxx-sed-4.3.patch: Fix build with sed 4.3, which is
  stricter regarding [[:space:]] vs [:space:]. configure.ac needs
  this to be represented as [[[:space:]]], as autoFOO itself
  swallows one pair of [].
- Add libtool BuildRequires and call to autoreconf, as above patch
  touches the build system.</changelog>
  <changelog author="adam@mizerski.pl" date="1492430400">- update to 5.0.1
  * See NEWS or https://github.com/jtv/libpqxx/blob/5.0.1/NEWS
    for details
- rebased libpqxx-sed-4.3.patch
- split doc subpackage</changelog>
  <changelog author="jengelh@inai.de" date="1492948800">- Select better RPM groups</changelog>
</package>
<package pkgid="a67702c6b418956b2dffc6383451b02478dee8cceb278b50292d47f7f00ae78f" name="libpqxx-doc" arch="noarch">
  <version epoch="0" ver="5.0.1" rel="40.2"/>
  <changelog author="crrodriguez@suse.de" date="1236945600">- remove static libraries</changelog>
  <changelog author="max@suse.de" date="1249300800">- New version: 3.0.1:
- All items marked as deprecated in the 2.x API have been removed.
- Fixed various problems in Visual C++ makefile for test suite.
- Fixed some problems with RPM packaging.
- Completely replaced cursor classes
- More helpful error messages on failed connections
- More detailed hierarchy of constraint-violation exception classes
- trigger is now called notify_listener, trigger header is now
  notify-listen
- New mixin base class pqxx_exception distinguishes libpqxx exception
  types
- Quoting is back! transaction_base::quote() &amp;
  connection_base::quote()
- Several build &amp; documentation problems with Visual C++ fixed
- Compile fixes for gcc 4.2, 4.3
- Uses strlcpy() where available, instead of strncpy()
- Keeps better track of applicable text encodings
- Fixed bug with prepared statement parameters in separate C++
  statements
- robusttransaction now works for multiple users
- Pipeline lets you cancel ongoing queries, e.g. because they run for
  too long
- Fixed broken escaping of binary values in tablewriter
- Floating-point types now represented with full precision
- Proper unit tests for new functionality
- New traits-based system for adding data types
- Floating-point infinities now supported
- Flushing/completing a pipeline now frees up the transaction for
  other use
- Completely reworked test suite, builds and runs much faster
- tablewriter supports writing of raw lines</changelog>
  <changelog author="max@suse.de" date="1266580800">- New version: 3.1:
- Shared libraries are now versioned by ABI: 3.1 instead of 3.1.0.
- Threading behaviour is now documented, and can be queried.
- Version information available at compile time.
- Supports parameterized statements.
- Result tuples now support slicing.
- Configure with --with-tr1=boost to use BOOST shared_ptr.
- String conversion now has its own header file.
- Supports read-only transactions.
- Uses shared_ptr if available.
- binarystring::str() is no longer cached; no longer returns
  reference.
- Lets you check whether a prepared statement has been defined.
- "Varargs" prepared statements.
- Unnamed prepared statements now supported.
- Results have iterator as well as const_iterator.
- Rewrite of robusttransaction logic; may actually do its job now.
- Connections support async query cancel from signal handler or
  thread.
- More documentation for performance features.</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- only use fdupes on 11.1 or newer</changelog>
  <changelog author="idonmez@novell.com" date="1306238400">- Add libpqxx-3.1-gcc46.patch, add missing cstddef include to
  fix compilation with gcc 4.6, upstream revision 1722</changelog>
  <changelog author="max@novell.com" date="1306324800">- Rename libpqxx-3.1-gcc46.patch to libpqxx-gcc46.patch.</changelog>
  <changelog author="aj@suse.de" date="1322913600">- Add require on pkg-config to provide pkg-config provides.
- Don't package libpqxx-3.1.so twice.</changelog>
  <changelog author="dimstar@opensuse.org" date="1332158400">- Add libpqxx-gcc47.patch: Fix build with gcc 4.7.</changelog>
  <changelog author="adam@mizerski.pl" date="1365508800">- update to 4.0.1
  * See NEWS or http://pqxx.org/development/libpqxx/browser/tags/4.0.1/NEWS
    for details.
- spec cleanup
  * Provide library in subpackage, which name follows
    shared library naming policy.
- removed libpqxx-rpmlintrc
  * it contained only addFilter("shlib-policy-name-error")
- removed patches libpqxx-gcc46.patch libpqxx-gcc47.patch -
  merged upstream.</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- add back buildroot to fix build on sle 11</changelog>
  <changelog author="dimstar@opensuse.org" date="1489492800">- Add libpqxx-sed-4.3.patch: Fix build with sed 4.3, which is
  stricter regarding [[:space:]] vs [:space:]. configure.ac needs
  this to be represented as [[[:space:]]], as autoFOO itself
  swallows one pair of [].
- Add libtool BuildRequires and call to autoreconf, as above patch
  touches the build system.</changelog>
  <changelog author="adam@mizerski.pl" date="1492430400">- update to 5.0.1
  * See NEWS or https://github.com/jtv/libpqxx/blob/5.0.1/NEWS
    for details
- rebased libpqxx-sed-4.3.patch
- split doc subpackage</changelog>
  <changelog author="jengelh@inai.de" date="1492948800">- Select better RPM groups</changelog>
</package>
<package pkgid="afdc008b6aac3365d7e1920602c642ee986e48008e449264db2817c28230c16e" name="pg_top" arch="src">
  <version epoch="0" ver="3.7.0" rel="2.2"/>
  <changelog author="poeml@suse.de" date="1234785600">- imported Fedora package (version 3.6.2)</changelog>
  <changelog author="max@suse.com" date="1349352000">- Explicitly require autoconf.</changelog>
  <changelog author="adam@mizerski.pl" date="1377950400">- update to 3.7.0
  - details in HISTORY
- dropped pg_top-libpq.patch
- added abuild.patch
- general packaging improvements</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- autoreconf --force alone was not enough (anymore), autoreconf -fi
  to the rescue.</changelog>
</package>
<package pkgid="94b155176562be3b7275f6ff6061d462844a627d73b81a2e2cb32ecc650b31a4" name="pg_top" arch="x86_64">
  <version epoch="0" ver="3.7.0" rel="2.2"/>
  <changelog author="poeml@suse.de" date="1234785600">- imported Fedora package (version 3.6.2)</changelog>
  <changelog author="max@suse.com" date="1349352000">- Explicitly require autoconf.</changelog>
  <changelog author="adam@mizerski.pl" date="1377950400">- update to 3.7.0
  - details in HISTORY
- dropped pg_top-libpq.patch
- added abuild.patch
- general packaging improvements</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- autoreconf --force alone was not enough (anymore), autoreconf -fi
  to the rescue.</changelog>
</package>
<package pkgid="3b6de5a2ec4bcfbeaa6696503ff63ad15f7bc30bf4a3f590c6f9d3ecf0ac994b" name="pg_top-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.7.0" rel="2.2"/>
  <changelog author="poeml@suse.de" date="1234785600">- imported Fedora package (version 3.6.2)</changelog>
  <changelog author="max@suse.com" date="1349352000">- Explicitly require autoconf.</changelog>
  <changelog author="adam@mizerski.pl" date="1377950400">- update to 3.7.0
  - details in HISTORY
- dropped pg_top-libpq.patch
- added abuild.patch
- general packaging improvements</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- autoreconf --force alone was not enough (anymore), autoreconf -fi
  to the rescue.</changelog>
</package>
<package pkgid="937ae94b7cc2c5afb25daf323095b34b1ca27aa7eebd56a1681aac3934faf55e" name="pg_top-debugsource" arch="x86_64">
  <version epoch="0" ver="3.7.0" rel="2.2"/>
  <changelog author="poeml@suse.de" date="1234785600">- imported Fedora package (version 3.6.2)</changelog>
  <changelog author="max@suse.com" date="1349352000">- Explicitly require autoconf.</changelog>
  <changelog author="adam@mizerski.pl" date="1377950400">- update to 3.7.0
  - details in HISTORY
- dropped pg_top-libpq.patch
- added abuild.patch
- general packaging improvements</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- autoreconf --force alone was not enough (anymore), autoreconf -fi
  to the rescue.</changelog>
</package>
<package pkgid="4b4968a40e80dd6c0ec622735eff91563f17e6dc64307efae9a1e75986f5f246" name="pgaccess" arch="noarch">
  <version epoch="0" ver="0.99.0.20040219" rel="24.1"/>
  <changelog author="max@suse.de" date="1051531200">- PgAccess was a subpackage of PostgreSQL before (postgresql-tk),
  but recently became a project of it's own.
- New snapshot version 0.98.8.20030117 .</changelog>
  <changelog author="max@suse.de" date="1060344000">- New version: 0.98.8.20030520.</changelog>
  <changelog author="hmacht@suse.de" date="1075982400">- added option # norootforbuild in specfile</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="max@suse.de" date="1259236800">- Version 0.99.0-20040219
- Package cleanup
- Fix startup problem (bnc#414190).</changelog>
  <changelog author="cfarrell@suse.com" date="1332849600">- license update: PostgreSQL
  SPDX format as per spdx.org/licenses/PostgreSQL</changelog>
</package>
<package pkgid="a92af15a81c19273b0cd19cc93dd9d450997b592d0379d109c6b341dfa55f30b" name="pgaccess" arch="src">
  <version epoch="0" ver="0.99.0.20040219" rel="24.1"/>
  <changelog author="max@suse.de" date="1051531200">- PgAccess was a subpackage of PostgreSQL before (postgresql-tk),
  but recently became a project of it's own.
- New snapshot version 0.98.8.20030117 .</changelog>
  <changelog author="max@suse.de" date="1060344000">- New version: 0.98.8.20030520.</changelog>
  <changelog author="hmacht@suse.de" date="1075982400">- added option # norootforbuild in specfile</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="max@suse.de" date="1259236800">- Version 0.99.0-20040219
- Package cleanup
- Fix startup problem (bnc#414190).</changelog>
  <changelog author="cfarrell@suse.com" date="1332849600">- license update: PostgreSQL
  SPDX format as per spdx.org/licenses/PostgreSQL</changelog>
</package>
<package pkgid="0883fc10fbdda454850dd6e2b4c53bfee48eb53c6f2bd4341d331ec3fced845d" name="pgadmin3" arch="src">
  <version epoch="0" ver="1.22.2" rel="39.4"/>
  <changelog author="saschpe@gmx.de" date="1296734400">- added dependency on wxWidgets for openSUSE-11.4 and greater</changelog>
  <changelog author="mrueckert@suse.de" date="1298980800">- use wx_requires on 11.4 and newer</changelog>
  <changelog author="klaussfreire@gmail.com" date="1301313600">- update to upstream git 2011-03-28</changelog>
  <changelog author="saschpe@suse.de" date="1302523200">- set license to 'PostgreSQL', fixes bnc#675943</changelog>
  <changelog author="klaussfreire@gmail.com" date="1316174400">- update to upstream 1.14.0
  * see http://www.pgadmin.org/development/changelog.php</changelog>
  <changelog author="coolo@suse.com" date="1322827200">- add automake as buildrequire to avoid implicit dependency</changelog>
  <changelog author="pascal.bleser@opensuse.org" date="1340539200">- update to 1.14.3:
  http://www.pgadmin.org/development/changelog.php</changelog>
  <changelog author="bruno@ioda-net.ch" date="1359374400">- fix bnc#800831
- update to 1.16.1
  http://www.pgadmin.org/development/changelog.php
    Date       Dev Ver     Change details
  - --------- --- ------  --------------
    2012-12-03 DP  1.16.1  Prevent a crash that could happen if further changes
  were made on a dialogue after using the Apply button.
  [Akshay Joshi]
    2012-11-29 GL  1.16.1  Save new comments on already existing columns when
  editing a table. Per a report from Jeff Janes.
    2012-11-29 GL  1.16.1  Fix the query editor behaviour when executing COPY TO
  stdout and COPY FROM stdin [Heikki Linnakangas]
    2012-11-28 AV  1.16.1  Date picker controls returns a full timestamp by
  default, which can cause inadvertent date changes
  on jobs and role validty dates. Ignore the time part.
    2012-11-26 MH  1.16.1  Fix query for database descriptions
    2012-11-15 DP  1.16.1  Avoid querying the catalogs for toast table settings
  for every table in the database. This gives a huge
  performance gain with large schemas.
    2012-11-08 DP  1.16.1  Prevent a crash when refreshing a node which has a
  child with an open dialogue [Dhiraj Chawla]
    2012-11-08 DP  1.16.1  Fix dropping/renaming of indexes [Akshay Joshi]
    2012-11-08 DP  1.16.1  Avoid updating the GQB model on every key press in
  the query tool [Dhiraj Chawla]
    2012-11-02 DP  1.16.1  Fix a crash that can occur when renaming objects.
  [Ashesh Vashi/Sachin Srivastava]
    2012-11-01 DP  1.16.1  Fix dropping of constraints [Akshay Joshi]
    2012-10-31 DP  1.16.1  Fix the "blocked by" column in the server status
  dialogue on 9.2 servers [Sachin Srivastava]
    2012-10-11 DP  1.16.1  Prevent a crash if the query tool is closed whilst a
  file is loading [Akshay Joshi]
    2012-10-09 AV  1.16.1  Fix setting of comments on PPAS procedures.
    2012-10-08 DP  1.16.1  Don't autosize the search results columns if no
  results are found [Akshay Joshi]
    2012-10-08 AV  1.16.1  Prevent a crash if opening a second config file in
  the editor.
    2012-10-08 DP  1.16.1  Prevent the SSL options combo box displaying
  duplicate options if the server dialogue is
  reopened [Akshay Joshi]
    2012-09-14 GL  1.16.1  Fix trigger query when connected to PostgreSQL 8.2 or
  lower, per a report from Jon Roberts.
    2012-09-12 GL  1.16.1  Fix message when executing an empty query, per Marc
  Mamin.
    2012-05-08 GL  1.16.0  Add privilege support on aggregates.
    2012-05-05 GL  1.16.0  Add inline function support on languages.
    2012-04-29 GL  1.16.0  Add support for range types.
    2012-04-28 GL  1.16.0  Add support for setting db/user config on dlgRole.
    2012-04-08 GL  1.16.0  Move references table textbox to the third tab in
  dlgForeignKey. Per request from Colin Beckingham.
    2012-04-05 GL  1.16.0  Support for the new two columns in 9.2 pg_stat_database
    2012-03-12 GL  1.16.0  Support for renaming constraints (9.2).
    2012-03-02 GL  1.16.0  Fix wxWidgets 2.9 compatibility with pgAdmin on Linux
  [Akshay Joshi].
    2012-02-23 GL  1.16.0  New import tool.
    2012-02-15 GL  1.16.0  Support for the LEAKPROOF option in functions.
    2012-02-13 GL  1.16.0  Support ANALYZE, CATEGORY, and PREFERED items for
  CREATE TYPE statement.
    2012-02-11 GL  1.16.0  Support CREATE TABLE LIKE.
    2012-02-09 GL  1.16.0  Support for the new TIMING option in EXPLAIN ANALYZE.
    2012-01-26 GL  1.16.0  Support for the new three columns in 9.2 pg_stat_database
    2012-01-22 GL  1.16.0  Use date_trunc to skip the microseconds part of all
  timestamp fields in frmStatus.
    2012-01-22 GL  1.16.0  Support new/changed pg_stat_activity fields.
    2012-01-08 GL  1.16.0  Allow renaming a domain.
    2012-01-07 GL  1.16.0  Add subitems to the schemas and catalogs in GQB.
  Request from Colin Beckingham.
    2012-01-05 GL  1.16.0  Support section options for pg_dump/pg_restore.
    2012-01-03 GL  1.16.0  Add security_barrier option handling for views.
    2011-12-19 DP  1.16.0  Add an "New Folder" button to the "Add Favourite" dialog
  in the query tool [Dhiraj Chawla]
    2011-12-12 GL  1.16.0  Support for the new sslcompression connection option.
    2011-12-11 GL  1.16.0  Add renaming of FDW and Server objects.
    2011-12-10 GL  1.16.0  Support for TRUNCATE permission
    2011-09-10 GL  1.16.0  Reverse engineering in the database designer.
  Patch from Luis Ochoa with some fixes by me.
    2011-09-04 GL  1.16.0  Highlight the other brace even if the current one is
  before the caret (request from Andreas).
    2011-08-24 DP  1.16.0  Add options to refresh objects automatically when
  clicked [Vinicius Santos]
    2011-08-15 GL  1.16.0  Redesign frmOptions.
    2011-08-11 GL  1.16.0  Prevents dropping connection, dropping or refreshing
  object when a properties dialog is open.
    2011-08-11 GL  1.16.0  Support for multimodels diagram in the database
  designer. Patch from Luis Ochoa with some fixes by me.
    2011-08-07 GL  1.16.0  Implement enable/disable save button, on text change.
  Patch from Vinicius Santos.
    2011-07-25 GL  1.16.0  Change doc build system.
    2011-07-25 GL  1.16.0  Support for security labels on global/shared objects
  (9.2 feature).
    2011-07-25 GL  1.16.0  Support for security labels on local objects (9.1
  feature).
    2011-07-25 GL  1.16.0  Support for non valid domains, and check constraints
  (9.2 feature).
    2011-07-25 GL  1.16.0  Add load/save support for the Database Designer. Patch
  from Luis Ochoa.
    2011-07-09 GL  1.16.0  Allow change of schema in the UI. Patch from Thom
  Brown.
    2011-07-05 GL  1.16.0  Add "Search Objects" dialog. Patch from Jasmin Dizdarevic.
    2011-07-03 GL  1.16.0  New maintenance action: CLUSTER. Patch from Thom Brown.
    2011-07-02 GL  1.16.0  Enable "Has OIDs" on 8.4+ even when the table is
  already created. Patch from Thom Brown.
    2011-06-27 GL  1.16.0  Add Database Designer. Patch from Luis Ochoa.
    2011-06-23 DP  1.16.0  Allow change of the fill factor. Patch from Thom Brown.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1382184000">- spec remove cleaning png2c (fixed in 1.18)
- update to 1.18.1
  http://www.pgadmin.org/development/changelog.php
  Date       Dev Ver     Change details
  - --------- --- ------  --------------
  2013-09-29 GL  1.18.1  Allow the dump of pg&lt;something&gt; schemas.
  2013-09-26 DP  1.18.1  Prevent a crash on Windows when dropping a column or a
  constraint on a table [Dhiraj Chawla]
  2013-09-26 DP  1.18.1  Ensure DDLScript will work with Slony 2.2+ which has a
  new SQL level API [Neel Patel]
  2013-09-26 DP  1.18.1  Fix ordering of object types in the display options and
  add Event Triggers which were missing [Dhiraj Chawla].
  2013-09-21 AV  1.18.1  Ensure the debugger can cope with functions that have an
  OUT parameter as the first.
  2013-09-19 DP  1.18.1  Fix the quoting of user mapping objects [Dinesh Kumar]
  2013-09-19 DP  1.18.1  Ensure that materialised views are available as targets
  for synonyms [Neel Patel]
  2013-09-19 DP  1.18.1  Fix the query used to find tables in a Slony
  replication set [Neel Patel]
  2013-09-11 DP  1.18.1  Prevent a crash if a user starts an external process
  such as a backup, and then immediately hits cancel
  [Neel Patel].
  2013-09-06 DP  1.18.1  Fix a memory leak in the Event Trigger code [Dinesh
  Kumar].
  2013-08-20 AV  1.18.0  Fix a layout bug in the graphical explain renderer that
  could render nodes on top of each other.
  2013-08-06 DP  1.18.0  Fix Slony's DDL Script support [Akshay Joshi].
  2013-07-26 DP  1.18.0  Add support for Event Triggers in 9.3+ [Dinesh Kumar].
  2013-07-22 DP  1.18.0  Avoid using a Help cache file that needs to be world
  writeable, and ensure sed is happy when post-processing
  helpfiles.
  2013-07-22 DP  1.18.0  Fix the help path on the import dialogue and improve the
  error handling [Akshay Joshi].
  2013-07-22 DP  1.18.0  Fix path the the Search Objects help doc [Dhiraj Chawla].
  2013-07-18 GL  1.18.0  Fix UTF-8 display for guru hints [Marek Cernocky].
  2013-07-08 DP  1.18.0  Prevent a crash when creating a stored procedure in
  PPAS [Dinesh Kumar].
  2013-06-19 GL  1.18.0  Disable the Favourites menu items if there is no
  favourites file path (per a comment from Michael Shapiro).
  2013-06-18 GL  1.18.0  Make No the default button on the Truncate confirmation
  dialog (per request from Humberto Cereser Ibanez).
  2013-06-18 DP  1.18.0  Support Materialized Views [Neel Patel].
  2013-06-07 DP  1.18.0  Avoid a possible crash on Linux when using the
  "Script" options of the Query Tool [aditsu].
  2013-05-26 DP  1.18.0  Fix comments on constraints [Thom Brown].
  2013-05-26 DP  1.18.0  Fix schema prefixes in cast definitions in the browser.
  2013-05-26 DP  1.18.0  Treat sequences as first class objects in the Grant
  Wizard. Support USAGE and remove obsolete RULE
  permissions [Dhiraj Chawla].
  2013-05-26 DP  1.18.0  Set the default backup type to "Custom".
  2013-05-21 DP  1.18.0  Improve the copy handling on the Edit Grid so that
  it works more consistently and predictably.
  2013-05-20 DP  1.18.0  Fix comments on columns.
  2013-05-20 DP  1.18.0  Remove the "Apply" buttons from the function, view
  package and external table dialogues. Their use is
  discouraged, and the code is fragile, complex and
  very buggy.
  2013-05-20 DP  1.18.0  Fix a crash that could occur if the browser fails to
  detect that an object has been changed by another
  session.
  2013-05-17 DP  1.18.0  Change the default SQL box font to a slightly smaller
  size on GTK based platforms.
  2013-05-17 DP  1.18.0  Don't prompt the user for a password if they're using
  a client certificate.
  2013-05-17 DP  1.18.0  Ensure global backups use the mintenance database to
  avoid access issue with postgres or template1.
  2013-05-17 DP  1.18.0  Fix SSL certificate authentication.
  2013-05-08 DP  1.18.0  Fix renaming and schema changes for stored procedures
  in PPAS [Dinesh Kumar].
  2013-05-02 DP  1.18.0  Add SSH tunnelling support to allow connections to be
  made to hosts via an SSH server [Akshay Joshi].
  2013-05-02 DP  1.18.0  Display the index validity in the properties list for
  indexes and index-based constraints [Gabrielle Roth].
  2013-04-29 DP  1.18.0  Add an option to include column headers when copying
  from the query tool results [Jasmin Dizdarevic].
  2013-04-29 DP  1.18.0  Allow the decimal mark displayed by the query tool to be
  configured as the thousands separator can [Jasmin
  Dizdarevic].
  2013-04-25 DP  1.18.0  Ensure the Query Tool's maximum column length setting
  is honoured.
  2013-04-22 DP  1.18.0  Handle default privileges to PUBLIC correctly. [Dhiraj
  Chawla].
  2013-03-24 GL  1.18.0  Add tab option in the Import dialog. Per a request from
  Jeff Janes.
  2013-03-17 GL  1.18.0  Add smallserial handling. Per a request from Matthew
  Syphus.
  2013-03-01 DP  1.18.0  Fix the editing of pg_hba.conf files [Dhiraj Chawla].
  2013-02-25 DP  1.18.0  Fix the display of extension owner names.
  2013-02-23 GL  1.18.0  Add a title to the backup and restore windows. Per
  request from Bastiaan Olij.
  2013-02-22 DP  1.18.0  Fix a bug that could cause a NOTICE to be displayed
  when rendering FTS Configurations in the tree.
  2013-02-07 DP  1.18.0  Don't try to display dependents or dependencies for
  pgAgent jobs, schedules or steps.
  2013-02-06 DP  1.18.0  Fix the handling of expiry times when modifying roles.
  2013-02-04 DP  1.18.0  Prevent foreign keys being recreated unnecessarily when
  modifying tables [Michael Banck]
  2013-01-24 DP  1.18.0  Prevent Cmd+S adding characters to the Query Tool when
  the Save button is disabled.
  2013-01-18 DP  1.18.0  Fix handling of Greenplum partitions [Lubomir Petrov]
  2013-01-06 GL  1.18.0  Add -V/--version CLI option.
  2013-01-06 GL  1.18.0  Add actions menu to the serverstatus tool.
  2013-01-06 GL  1.18.0  Fix the database SQL when reseting a configuration
  parameter. Per a report from Bartosz Dmytrak.
  2013-01-04 GL  1.18.0  Refresh the toolbar buttons when a list has been
  updated. Per a report from Evan Martin.
  2013-01-04 GL  1.18.0  Fix the "NO INHERIT" query. Report from Thomas Joseph.
  2012-12-24 GL  1.18.0  Display default privs. Report from Nathan Alden.
  2012-12-24 GL  1.18.0  Sort references by schema name and relation name in
  dlgForeignKey. Report from Michal Kozusznik.
  2012-12-24 GL  1.18.0  Fix the change of the superuser attribute. Report from
  Michal Kozusznik.
  2012-12-18 DP  1.18.0  Prevent a crash when using Cmd-A on a file loaded into
  the Query Tool when opened with Cmd-E on Mac.
  2012-12-07 DP  1.18.0  Fix the queries used to get object comments to allow
  for duplicate OIDs that may be present following use
  of pg_upgrade.</changelog>
  <changelog author="max@suse.com" date="1386849600">- Remove broken and unneeded dependency on libecpg (bnc#854754).</changelog>
  <changelog author="termim@gmail.com" date="1422446400">- update to 1.20.0
  * Resolving the inconsistency of preservation of modified
    information of the columns, while adding/editing a table from
    the table dialog
  * Add missing nodes to graphical explain plan
  * Fix the Resource Groups dialog - separated the statements,
    which can not be ran in single transaction
  * Support for Slony-I 2.2+ with PostgreSQL 9.3+
  * Support smallserial columns in Edit Data Window
  * Restore the user specified size on the grid (which contains the
    result) in Query windows to fix an issue related to the column
    size is too narrow on subsequent Explain execution
  * Empty the Undo/Redo history everytime new file is opened
  * Added accelerator F8 for 'Execute to file' in the Query window
  * Beautify the query shown in the SQL pane for the functions
    having multiple arguments by adding new lines with small
    modification
  * Check for the columnlist for the UPDATE OF syntax on trigger
    also works with PPAS 9.5+
  * Proper saving of columns width in the server status window
  * CHECK OPTION is applicable to the views only, and not the
    materialized views
  * Prevent a crash during the update of the macro or favourite
    list
  * Allow quick injectection of favourites by name
  * Fix handling of saving macros after pasting a query in the box
  * Fix handling of char()[] columns in the Edit Grid
  * Support the new check_option parameter of views
  * Handle the 9.4 MOVE clause of ALTER TABLESPACE
  * Add a new action menu to refresh a materialized view
  * Support the new 9.4 columns in pg_stat_activity
  * Save search options for next time
  * Ensure Favourite queries are only saved when the OK button is
    pressed
  * Fix an issue refreshing functions in PPAS packages
  * Improve handling of lost connections
  * Allow searching for database objects by comment and definition
    content
  * Add support for Resource Groups in PPAS 9.4
  * Add Save and Exit shortcut keys to the edit grid
  * Enable backward search in SQL Box using Shift + F3
  * Allow more flexible selection/deselection of rows and columns
    in Edit Grid
  * Allow more options with the plain backup.
  * Use a much smarter auto-sizing algorithm for the columns in the
    Query Tool output grid.
  * Remember the last panel used on the Options dialogue, and
    display the default panel if a group node is selected on the
    tree
  * Allow parallel dump with -j starting with 9.3
- update to 1.18.2
  * Fix SQL for GRANT on a sequence. Report from liuyuanyuan.
  * Fix escape handling in pgpass files
  * GQB forgot the materialized views.
  * Don't set log_min_messages from the debugger
  * Fix a crash on OSX when run explain through shortcut in query
    editor, when mouse is over a existing shape, and popup, showing
    the step information, is on
  * Using the GetOid() function instead of GetLong() for Oid
    columns
  * Fix SQL comments for inherited columns.
  * Flush the changes in the settings as soon as new server is
    added
  * Don't include obsolete config settings from &lt;= 8.3 in the
    config editor unless running on an appropriate server.
  * Ensure the Type dialogue detects name changes.
  * Ensure report titles don't overflow the page width
  * Ensure reports overflow the page width properly
  * Add missing "port" option for SSH tunnels.
  * Set 32bit PostgreSQL, EnterpriseDB PATH (in case - 64bit
    respective applications not found, and 32bit(s) are available)
    for 64bit pgAdmin III.
  * Improved the debugger to work better with PPAS &lt;= 9.2
  * Fix the handling of the "Valid Until" date/time on the role
    dialogue on Mac.</changelog>
  <changelog author="mpluskal@suse.com" date="1439380800">- Add explicit dependencies on autoconf and libtool</changelog>
  <changelog author="jweberhofer@weberhofer.at" date="1444996800">- Do not recommend but only suggest to install postgresql-server.</changelog>
  <changelog author="termim@gmail.com" date="1453809600">- update to 1.22.0
  * Resolved an issue related to check options selection in the view
    properties dialog with the check option.
  * Merged the libssh2 to the latest version.
  * Properly detect serial columns as such when identifiers have been
    truncated.
  * Fixes an issue related to the column inheritance information properly,
    when one (or, more) common columns are inherited from multiple tables.
  * Ensure the correct syntax used for moving the objects from one
    tablespace to another.
  * Ensure the correct line endings are used when copying from the SQL Pane
  * Toolbar icons, and menu items for Commit and Rollback actions.
  * Display the connection details for the current browser object in the
    status bar
  * Fixed an issue related to different menus enabling in the Query Tool on
    Ubunutu unity.
  * Reset the position (x, y) for dialog(s), and frame(s) to 0 (if found
    negative), while saving its position and size.
  * Fixes an issue identifying the return type to TABLE in some cases,
    using pg_get_function_result(..) for the same instead of format_type(..)
  * Honour PGPASSFILE environment variable for saving, retrieving the
    password instead of always works with pgpass.conf (on windows)/.pgpass
    (on non-windows)
  * Fix a segfault occurs while detecting transaction section requirement,
    when autocommit has been disabled.
  * Format execution time in a more readable manner
  * Improve sorting in Data editor
  * Allow to format the selecte SQL using external tools in Query Editor
  * Allow to set auto-commit mode to on/off in the query editor
  * Do not try unlock the mutex, which was not owned by the thread, while
    creating the popup menu
  * Set the focus on browser tree windows on startup
  * Make the arrow key navigation consistent across all platform on the
    object browser tree
  * Show indexes for the materialized views in Query pane
  * Add support for searching materialized views in the</changelog>
  <changelog author="crrodriguez@opensuse.org" date="1456660800">- remove obsolete suse_version checks
- fix debuginfo generation.</changelog>
  <changelog author="crrodriguez@opensuse.org" date="1456660801">- Update to version 1.22.1
  * Don't barf when connecting to Greenplum or Greenplum HAWQ
  * Fix selection of conversion functions in the CREATE CONVERSION dialogue.
  * Properly quote type names in the Type dialogue, andensure range
  information is displayed for existing types
  * Fix selection of cast functions in the Cast dialogue</changelog>
  <changelog author="martin.liska@suse.com" date="1467374400">- Add -fno-delete-null-pointer-checks to CXXFLAGS to workaround
  boo#986857.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to version 1.22.2
  * Include the Negator when reverse engineering SQL for operators
  * Fix the psql plugin command on OSX to work more reliably
  * Prevent a crash in some situtions where the database connection
  is lost and needs to be reset.
  * Fix display of elapsed query time for queries running longer than
  1 hour
- This is the final release of pgadmin3</changelog>
  <changelog author="bruno@ioda-net.ch" date="1485691200">- Packaging :
  + spec-clean minimal
  + remove obsolete version sle and openSUSE
  + globalize \r removal in css files
  + use wxWidgets-3_0-nostl-devel to remove dependency of gst 0.10
    so use internal dependency generator on openSUSE &gt; 1315
  + Add WX_VER variable to build correctly
  + Added patch wxWidget-limit-libs-used.patch to explicitely add
    the needed libs.
  + Try to handle differents WX versions between openSUSE and SLE</changelog>
  <changelog author="bruno@ioda-net.ch" date="1492516800">- Add 0001-Set-row-heights-based-on-pixels-rather-than-points.patch
  Fix control grid row on hidpi screen.</changelog>
</package>
<package pkgid="6c8ff9c0f35e6094b6cddff115bd4542e390e02f5e222f119ac616c34205bac1" name="pgadmin3" arch="x86_64">
  <version epoch="0" ver="1.22.2" rel="39.4"/>
  <changelog author="saschpe@gmx.de" date="1296734400">- added dependency on wxWidgets for openSUSE-11.4 and greater</changelog>
  <changelog author="mrueckert@suse.de" date="1298980800">- use wx_requires on 11.4 and newer</changelog>
  <changelog author="klaussfreire@gmail.com" date="1301313600">- update to upstream git 2011-03-28</changelog>
  <changelog author="saschpe@suse.de" date="1302523200">- set license to 'PostgreSQL', fixes bnc#675943</changelog>
  <changelog author="klaussfreire@gmail.com" date="1316174400">- update to upstream 1.14.0
  * see http://www.pgadmin.org/development/changelog.php</changelog>
  <changelog author="coolo@suse.com" date="1322827200">- add automake as buildrequire to avoid implicit dependency</changelog>
  <changelog author="pascal.bleser@opensuse.org" date="1340539200">- update to 1.14.3:
  http://www.pgadmin.org/development/changelog.php</changelog>
  <changelog author="bruno@ioda-net.ch" date="1359374400">- fix bnc#800831
- update to 1.16.1
  http://www.pgadmin.org/development/changelog.php
    Date       Dev Ver     Change details
  - --------- --- ------  --------------
    2012-12-03 DP  1.16.1  Prevent a crash that could happen if further changes
  were made on a dialogue after using the Apply button.
  [Akshay Joshi]
    2012-11-29 GL  1.16.1  Save new comments on already existing columns when
  editing a table. Per a report from Jeff Janes.
    2012-11-29 GL  1.16.1  Fix the query editor behaviour when executing COPY TO
  stdout and COPY FROM stdin [Heikki Linnakangas]
    2012-11-28 AV  1.16.1  Date picker controls returns a full timestamp by
  default, which can cause inadvertent date changes
  on jobs and role validty dates. Ignore the time part.
    2012-11-26 MH  1.16.1  Fix query for database descriptions
    2012-11-15 DP  1.16.1  Avoid querying the catalogs for toast table settings
  for every table in the database. This gives a huge
  performance gain with large schemas.
    2012-11-08 DP  1.16.1  Prevent a crash when refreshing a node which has a
  child with an open dialogue [Dhiraj Chawla]
    2012-11-08 DP  1.16.1  Fix dropping/renaming of indexes [Akshay Joshi]
    2012-11-08 DP  1.16.1  Avoid updating the GQB model on every key press in
  the query tool [Dhiraj Chawla]
    2012-11-02 DP  1.16.1  Fix a crash that can occur when renaming objects.
  [Ashesh Vashi/Sachin Srivastava]
    2012-11-01 DP  1.16.1  Fix dropping of constraints [Akshay Joshi]
    2012-10-31 DP  1.16.1  Fix the "blocked by" column in the server status
  dialogue on 9.2 servers [Sachin Srivastava]
    2012-10-11 DP  1.16.1  Prevent a crash if the query tool is closed whilst a
  file is loading [Akshay Joshi]
    2012-10-09 AV  1.16.1  Fix setting of comments on PPAS procedures.
    2012-10-08 DP  1.16.1  Don't autosize the search results columns if no
  results are found [Akshay Joshi]
    2012-10-08 AV  1.16.1  Prevent a crash if opening a second config file in
  the editor.
    2012-10-08 DP  1.16.1  Prevent the SSL options combo box displaying
  duplicate options if the server dialogue is
  reopened [Akshay Joshi]
    2012-09-14 GL  1.16.1  Fix trigger query when connected to PostgreSQL 8.2 or
  lower, per a report from Jon Roberts.
    2012-09-12 GL  1.16.1  Fix message when executing an empty query, per Marc
  Mamin.
    2012-05-08 GL  1.16.0  Add privilege support on aggregates.
    2012-05-05 GL  1.16.0  Add inline function support on languages.
    2012-04-29 GL  1.16.0  Add support for range types.
    2012-04-28 GL  1.16.0  Add support for setting db/user config on dlgRole.
    2012-04-08 GL  1.16.0  Move references table textbox to the third tab in
  dlgForeignKey. Per request from Colin Beckingham.
    2012-04-05 GL  1.16.0  Support for the new two columns in 9.2 pg_stat_database
    2012-03-12 GL  1.16.0  Support for renaming constraints (9.2).
    2012-03-02 GL  1.16.0  Fix wxWidgets 2.9 compatibility with pgAdmin on Linux
  [Akshay Joshi].
    2012-02-23 GL  1.16.0  New import tool.
    2012-02-15 GL  1.16.0  Support for the LEAKPROOF option in functions.
    2012-02-13 GL  1.16.0  Support ANALYZE, CATEGORY, and PREFERED items for
  CREATE TYPE statement.
    2012-02-11 GL  1.16.0  Support CREATE TABLE LIKE.
    2012-02-09 GL  1.16.0  Support for the new TIMING option in EXPLAIN ANALYZE.
    2012-01-26 GL  1.16.0  Support for the new three columns in 9.2 pg_stat_database
    2012-01-22 GL  1.16.0  Use date_trunc to skip the microseconds part of all
  timestamp fields in frmStatus.
    2012-01-22 GL  1.16.0  Support new/changed pg_stat_activity fields.
    2012-01-08 GL  1.16.0  Allow renaming a domain.
    2012-01-07 GL  1.16.0  Add subitems to the schemas and catalogs in GQB.
  Request from Colin Beckingham.
    2012-01-05 GL  1.16.0  Support section options for pg_dump/pg_restore.
    2012-01-03 GL  1.16.0  Add security_barrier option handling for views.
    2011-12-19 DP  1.16.0  Add an "New Folder" button to the "Add Favourite" dialog
  in the query tool [Dhiraj Chawla]
    2011-12-12 GL  1.16.0  Support for the new sslcompression connection option.
    2011-12-11 GL  1.16.0  Add renaming of FDW and Server objects.
    2011-12-10 GL  1.16.0  Support for TRUNCATE permission
    2011-09-10 GL  1.16.0  Reverse engineering in the database designer.
  Patch from Luis Ochoa with some fixes by me.
    2011-09-04 GL  1.16.0  Highlight the other brace even if the current one is
  before the caret (request from Andreas).
    2011-08-24 DP  1.16.0  Add options to refresh objects automatically when
  clicked [Vinicius Santos]
    2011-08-15 GL  1.16.0  Redesign frmOptions.
    2011-08-11 GL  1.16.0  Prevents dropping connection, dropping or refreshing
  object when a properties dialog is open.
    2011-08-11 GL  1.16.0  Support for multimodels diagram in the database
  designer. Patch from Luis Ochoa with some fixes by me.
    2011-08-07 GL  1.16.0  Implement enable/disable save button, on text change.
  Patch from Vinicius Santos.
    2011-07-25 GL  1.16.0  Change doc build system.
    2011-07-25 GL  1.16.0  Support for security labels on global/shared objects
  (9.2 feature).
    2011-07-25 GL  1.16.0  Support for security labels on local objects (9.1
  feature).
    2011-07-25 GL  1.16.0  Support for non valid domains, and check constraints
  (9.2 feature).
    2011-07-25 GL  1.16.0  Add load/save support for the Database Designer. Patch
  from Luis Ochoa.
    2011-07-09 GL  1.16.0  Allow change of schema in the UI. Patch from Thom
  Brown.
    2011-07-05 GL  1.16.0  Add "Search Objects" dialog. Patch from Jasmin Dizdarevic.
    2011-07-03 GL  1.16.0  New maintenance action: CLUSTER. Patch from Thom Brown.
    2011-07-02 GL  1.16.0  Enable "Has OIDs" on 8.4+ even when the table is
  already created. Patch from Thom Brown.
    2011-06-27 GL  1.16.0  Add Database Designer. Patch from Luis Ochoa.
    2011-06-23 DP  1.16.0  Allow change of the fill factor. Patch from Thom Brown.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1382184000">- spec remove cleaning png2c (fixed in 1.18)
- update to 1.18.1
  http://www.pgadmin.org/development/changelog.php
  Date       Dev Ver     Change details
  - --------- --- ------  --------------
  2013-09-29 GL  1.18.1  Allow the dump of pg&lt;something&gt; schemas.
  2013-09-26 DP  1.18.1  Prevent a crash on Windows when dropping a column or a
  constraint on a table [Dhiraj Chawla]
  2013-09-26 DP  1.18.1  Ensure DDLScript will work with Slony 2.2+ which has a
  new SQL level API [Neel Patel]
  2013-09-26 DP  1.18.1  Fix ordering of object types in the display options and
  add Event Triggers which were missing [Dhiraj Chawla].
  2013-09-21 AV  1.18.1  Ensure the debugger can cope with functions that have an
  OUT parameter as the first.
  2013-09-19 DP  1.18.1  Fix the quoting of user mapping objects [Dinesh Kumar]
  2013-09-19 DP  1.18.1  Ensure that materialised views are available as targets
  for synonyms [Neel Patel]
  2013-09-19 DP  1.18.1  Fix the query used to find tables in a Slony
  replication set [Neel Patel]
  2013-09-11 DP  1.18.1  Prevent a crash if a user starts an external process
  such as a backup, and then immediately hits cancel
  [Neel Patel].
  2013-09-06 DP  1.18.1  Fix a memory leak in the Event Trigger code [Dinesh
  Kumar].
  2013-08-20 AV  1.18.0  Fix a layout bug in the graphical explain renderer that
  could render nodes on top of each other.
  2013-08-06 DP  1.18.0  Fix Slony's DDL Script support [Akshay Joshi].
  2013-07-26 DP  1.18.0  Add support for Event Triggers in 9.3+ [Dinesh Kumar].
  2013-07-22 DP  1.18.0  Avoid using a Help cache file that needs to be world
  writeable, and ensure sed is happy when post-processing
  helpfiles.
  2013-07-22 DP  1.18.0  Fix the help path on the import dialogue and improve the
  error handling [Akshay Joshi].
  2013-07-22 DP  1.18.0  Fix path the the Search Objects help doc [Dhiraj Chawla].
  2013-07-18 GL  1.18.0  Fix UTF-8 display for guru hints [Marek Cernocky].
  2013-07-08 DP  1.18.0  Prevent a crash when creating a stored procedure in
  PPAS [Dinesh Kumar].
  2013-06-19 GL  1.18.0  Disable the Favourites menu items if there is no
  favourites file path (per a comment from Michael Shapiro).
  2013-06-18 GL  1.18.0  Make No the default button on the Truncate confirmation
  dialog (per request from Humberto Cereser Ibanez).
  2013-06-18 DP  1.18.0  Support Materialized Views [Neel Patel].
  2013-06-07 DP  1.18.0  Avoid a possible crash on Linux when using the
  "Script" options of the Query Tool [aditsu].
  2013-05-26 DP  1.18.0  Fix comments on constraints [Thom Brown].
  2013-05-26 DP  1.18.0  Fix schema prefixes in cast definitions in the browser.
  2013-05-26 DP  1.18.0  Treat sequences as first class objects in the Grant
  Wizard. Support USAGE and remove obsolete RULE
  permissions [Dhiraj Chawla].
  2013-05-26 DP  1.18.0  Set the default backup type to "Custom".
  2013-05-21 DP  1.18.0  Improve the copy handling on the Edit Grid so that
  it works more consistently and predictably.
  2013-05-20 DP  1.18.0  Fix comments on columns.
  2013-05-20 DP  1.18.0  Remove the "Apply" buttons from the function, view
  package and external table dialogues. Their use is
  discouraged, and the code is fragile, complex and
  very buggy.
  2013-05-20 DP  1.18.0  Fix a crash that could occur if the browser fails to
  detect that an object has been changed by another
  session.
  2013-05-17 DP  1.18.0  Change the default SQL box font to a slightly smaller
  size on GTK based platforms.
  2013-05-17 DP  1.18.0  Don't prompt the user for a password if they're using
  a client certificate.
  2013-05-17 DP  1.18.0  Ensure global backups use the mintenance database to
  avoid access issue with postgres or template1.
  2013-05-17 DP  1.18.0  Fix SSL certificate authentication.
  2013-05-08 DP  1.18.0  Fix renaming and schema changes for stored procedures
  in PPAS [Dinesh Kumar].
  2013-05-02 DP  1.18.0  Add SSH tunnelling support to allow connections to be
  made to hosts via an SSH server [Akshay Joshi].
  2013-05-02 DP  1.18.0  Display the index validity in the properties list for
  indexes and index-based constraints [Gabrielle Roth].
  2013-04-29 DP  1.18.0  Add an option to include column headers when copying
  from the query tool results [Jasmin Dizdarevic].
  2013-04-29 DP  1.18.0  Allow the decimal mark displayed by the query tool to be
  configured as the thousands separator can [Jasmin
  Dizdarevic].
  2013-04-25 DP  1.18.0  Ensure the Query Tool's maximum column length setting
  is honoured.
  2013-04-22 DP  1.18.0  Handle default privileges to PUBLIC correctly. [Dhiraj
  Chawla].
  2013-03-24 GL  1.18.0  Add tab option in the Import dialog. Per a request from
  Jeff Janes.
  2013-03-17 GL  1.18.0  Add smallserial handling. Per a request from Matthew
  Syphus.
  2013-03-01 DP  1.18.0  Fix the editing of pg_hba.conf files [Dhiraj Chawla].
  2013-02-25 DP  1.18.0  Fix the display of extension owner names.
  2013-02-23 GL  1.18.0  Add a title to the backup and restore windows. Per
  request from Bastiaan Olij.
  2013-02-22 DP  1.18.0  Fix a bug that could cause a NOTICE to be displayed
  when rendering FTS Configurations in the tree.
  2013-02-07 DP  1.18.0  Don't try to display dependents or dependencies for
  pgAgent jobs, schedules or steps.
  2013-02-06 DP  1.18.0  Fix the handling of expiry times when modifying roles.
  2013-02-04 DP  1.18.0  Prevent foreign keys being recreated unnecessarily when
  modifying tables [Michael Banck]
  2013-01-24 DP  1.18.0  Prevent Cmd+S adding characters to the Query Tool when
  the Save button is disabled.
  2013-01-18 DP  1.18.0  Fix handling of Greenplum partitions [Lubomir Petrov]
  2013-01-06 GL  1.18.0  Add -V/--version CLI option.
  2013-01-06 GL  1.18.0  Add actions menu to the serverstatus tool.
  2013-01-06 GL  1.18.0  Fix the database SQL when reseting a configuration
  parameter. Per a report from Bartosz Dmytrak.
  2013-01-04 GL  1.18.0  Refresh the toolbar buttons when a list has been
  updated. Per a report from Evan Martin.
  2013-01-04 GL  1.18.0  Fix the "NO INHERIT" query. Report from Thomas Joseph.
  2012-12-24 GL  1.18.0  Display default privs. Report from Nathan Alden.
  2012-12-24 GL  1.18.0  Sort references by schema name and relation name in
  dlgForeignKey. Report from Michal Kozusznik.
  2012-12-24 GL  1.18.0  Fix the change of the superuser attribute. Report from
  Michal Kozusznik.
  2012-12-18 DP  1.18.0  Prevent a crash when using Cmd-A on a file loaded into
  the Query Tool when opened with Cmd-E on Mac.
  2012-12-07 DP  1.18.0  Fix the queries used to get object comments to allow
  for duplicate OIDs that may be present following use
  of pg_upgrade.</changelog>
  <changelog author="max@suse.com" date="1386849600">- Remove broken and unneeded dependency on libecpg (bnc#854754).</changelog>
  <changelog author="termim@gmail.com" date="1422446400">- update to 1.20.0
  * Resolving the inconsistency of preservation of modified
    information of the columns, while adding/editing a table from
    the table dialog
  * Add missing nodes to graphical explain plan
  * Fix the Resource Groups dialog - separated the statements,
    which can not be ran in single transaction
  * Support for Slony-I 2.2+ with PostgreSQL 9.3+
  * Support smallserial columns in Edit Data Window
  * Restore the user specified size on the grid (which contains the
    result) in Query windows to fix an issue related to the column
    size is too narrow on subsequent Explain execution
  * Empty the Undo/Redo history everytime new file is opened
  * Added accelerator F8 for 'Execute to file' in the Query window
  * Beautify the query shown in the SQL pane for the functions
    having multiple arguments by adding new lines with small
    modification
  * Check for the columnlist for the UPDATE OF syntax on trigger
    also works with PPAS 9.5+
  * Proper saving of columns width in the server status window
  * CHECK OPTION is applicable to the views only, and not the
    materialized views
  * Prevent a crash during the update of the macro or favourite
    list
  * Allow quick injectection of favourites by name
  * Fix handling of saving macros after pasting a query in the box
  * Fix handling of char()[] columns in the Edit Grid
  * Support the new check_option parameter of views
  * Handle the 9.4 MOVE clause of ALTER TABLESPACE
  * Add a new action menu to refresh a materialized view
  * Support the new 9.4 columns in pg_stat_activity
  * Save search options for next time
  * Ensure Favourite queries are only saved when the OK button is
    pressed
  * Fix an issue refreshing functions in PPAS packages
  * Improve handling of lost connections
  * Allow searching for database objects by comment and definition
    content
  * Add support for Resource Groups in PPAS 9.4
  * Add Save and Exit shortcut keys to the edit grid
  * Enable backward search in SQL Box using Shift + F3
  * Allow more flexible selection/deselection of rows and columns
    in Edit Grid
  * Allow more options with the plain backup.
  * Use a much smarter auto-sizing algorithm for the columns in the
    Query Tool output grid.
  * Remember the last panel used on the Options dialogue, and
    display the default panel if a group node is selected on the
    tree
  * Allow parallel dump with -j starting with 9.3
- update to 1.18.2
  * Fix SQL for GRANT on a sequence. Report from liuyuanyuan.
  * Fix escape handling in pgpass files
  * GQB forgot the materialized views.
  * Don't set log_min_messages from the debugger
  * Fix a crash on OSX when run explain through shortcut in query
    editor, when mouse is over a existing shape, and popup, showing
    the step information, is on
  * Using the GetOid() function instead of GetLong() for Oid
    columns
  * Fix SQL comments for inherited columns.
  * Flush the changes in the settings as soon as new server is
    added
  * Don't include obsolete config settings from &lt;= 8.3 in the
    config editor unless running on an appropriate server.
  * Ensure the Type dialogue detects name changes.
  * Ensure report titles don't overflow the page width
  * Ensure reports overflow the page width properly
  * Add missing "port" option for SSH tunnels.
  * Set 32bit PostgreSQL, EnterpriseDB PATH (in case - 64bit
    respective applications not found, and 32bit(s) are available)
    for 64bit pgAdmin III.
  * Improved the debugger to work better with PPAS &lt;= 9.2
  * Fix the handling of the "Valid Until" date/time on the role
    dialogue on Mac.</changelog>
  <changelog author="mpluskal@suse.com" date="1439380800">- Add explicit dependencies on autoconf and libtool</changelog>
  <changelog author="jweberhofer@weberhofer.at" date="1444996800">- Do not recommend but only suggest to install postgresql-server.</changelog>
  <changelog author="termim@gmail.com" date="1453809600">- update to 1.22.0
  * Resolved an issue related to check options selection in the view
    properties dialog with the check option.
  * Merged the libssh2 to the latest version.
  * Properly detect serial columns as such when identifiers have been
    truncated.
  * Fixes an issue related to the column inheritance information properly,
    when one (or, more) common columns are inherited from multiple tables.
  * Ensure the correct syntax used for moving the objects from one
    tablespace to another.
  * Ensure the correct line endings are used when copying from the SQL Pane
  * Toolbar icons, and menu items for Commit and Rollback actions.
  * Display the connection details for the current browser object in the
    status bar
  * Fixed an issue related to different menus enabling in the Query Tool on
    Ubunutu unity.
  * Reset the position (x, y) for dialog(s), and frame(s) to 0 (if found
    negative), while saving its position and size.
  * Fixes an issue identifying the return type to TABLE in some cases,
    using pg_get_function_result(..) for the same instead of format_type(..)
  * Honour PGPASSFILE environment variable for saving, retrieving the
    password instead of always works with pgpass.conf (on windows)/.pgpass
    (on non-windows)
  * Fix a segfault occurs while detecting transaction section requirement,
    when autocommit has been disabled.
  * Format execution time in a more readable manner
  * Improve sorting in Data editor
  * Allow to format the selecte SQL using external tools in Query Editor
  * Allow to set auto-commit mode to on/off in the query editor
  * Do not try unlock the mutex, which was not owned by the thread, while
    creating the popup menu
  * Set the focus on browser tree windows on startup
  * Make the arrow key navigation consistent across all platform on the
    object browser tree
  * Show indexes for the materialized views in Query pane
  * Add support for searching materialized views in the</changelog>
  <changelog author="crrodriguez@opensuse.org" date="1456660800">- remove obsolete suse_version checks
- fix debuginfo generation.</changelog>
  <changelog author="crrodriguez@opensuse.org" date="1456660801">- Update to version 1.22.1
  * Don't barf when connecting to Greenplum or Greenplum HAWQ
  * Fix selection of conversion functions in the CREATE CONVERSION dialogue.
  * Properly quote type names in the Type dialogue, andensure range
  information is displayed for existing types
  * Fix selection of cast functions in the Cast dialogue</changelog>
  <changelog author="martin.liska@suse.com" date="1467374400">- Add -fno-delete-null-pointer-checks to CXXFLAGS to workaround
  boo#986857.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to version 1.22.2
  * Include the Negator when reverse engineering SQL for operators
  * Fix the psql plugin command on OSX to work more reliably
  * Prevent a crash in some situtions where the database connection
  is lost and needs to be reset.
  * Fix display of elapsed query time for queries running longer than
  1 hour
- This is the final release of pgadmin3</changelog>
  <changelog author="bruno@ioda-net.ch" date="1485691200">- Packaging :
  + spec-clean minimal
  + remove obsolete version sle and openSUSE
  + globalize \r removal in css files
  + use wxWidgets-3_0-nostl-devel to remove dependency of gst 0.10
    so use internal dependency generator on openSUSE &gt; 1315
  + Add WX_VER variable to build correctly
  + Added patch wxWidget-limit-libs-used.patch to explicitely add
    the needed libs.
  + Try to handle differents WX versions between openSUSE and SLE</changelog>
  <changelog author="bruno@ioda-net.ch" date="1492516800">- Add 0001-Set-row-heights-based-on-pixels-rather-than-points.patch
  Fix control grid row on hidpi screen.</changelog>
</package>
<package pkgid="2a4bbf4a6ea346d6935904b3fc13ffa16c70304b95ad28ed36b1669710f03dca" name="pgadmin3-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.22.2" rel="39.4"/>
  <changelog author="saschpe@gmx.de" date="1296734400">- added dependency on wxWidgets for openSUSE-11.4 and greater</changelog>
  <changelog author="mrueckert@suse.de" date="1298980800">- use wx_requires on 11.4 and newer</changelog>
  <changelog author="klaussfreire@gmail.com" date="1301313600">- update to upstream git 2011-03-28</changelog>
  <changelog author="saschpe@suse.de" date="1302523200">- set license to 'PostgreSQL', fixes bnc#675943</changelog>
  <changelog author="klaussfreire@gmail.com" date="1316174400">- update to upstream 1.14.0
  * see http://www.pgadmin.org/development/changelog.php</changelog>
  <changelog author="coolo@suse.com" date="1322827200">- add automake as buildrequire to avoid implicit dependency</changelog>
  <changelog author="pascal.bleser@opensuse.org" date="1340539200">- update to 1.14.3:
  http://www.pgadmin.org/development/changelog.php</changelog>
  <changelog author="bruno@ioda-net.ch" date="1359374400">- fix bnc#800831
- update to 1.16.1
  http://www.pgadmin.org/development/changelog.php
    Date       Dev Ver     Change details
  - --------- --- ------  --------------
    2012-12-03 DP  1.16.1  Prevent a crash that could happen if further changes
  were made on a dialogue after using the Apply button.
  [Akshay Joshi]
    2012-11-29 GL  1.16.1  Save new comments on already existing columns when
  editing a table. Per a report from Jeff Janes.
    2012-11-29 GL  1.16.1  Fix the query editor behaviour when executing COPY TO
  stdout and COPY FROM stdin [Heikki Linnakangas]
    2012-11-28 AV  1.16.1  Date picker controls returns a full timestamp by
  default, which can cause inadvertent date changes
  on jobs and role validty dates. Ignore the time part.
    2012-11-26 MH  1.16.1  Fix query for database descriptions
    2012-11-15 DP  1.16.1  Avoid querying the catalogs for toast table settings
  for every table in the database. This gives a huge
  performance gain with large schemas.
    2012-11-08 DP  1.16.1  Prevent a crash when refreshing a node which has a
  child with an open dialogue [Dhiraj Chawla]
    2012-11-08 DP  1.16.1  Fix dropping/renaming of indexes [Akshay Joshi]
    2012-11-08 DP  1.16.1  Avoid updating the GQB model on every key press in
  the query tool [Dhiraj Chawla]
    2012-11-02 DP  1.16.1  Fix a crash that can occur when renaming objects.
  [Ashesh Vashi/Sachin Srivastava]
    2012-11-01 DP  1.16.1  Fix dropping of constraints [Akshay Joshi]
    2012-10-31 DP  1.16.1  Fix the "blocked by" column in the server status
  dialogue on 9.2 servers [Sachin Srivastava]
    2012-10-11 DP  1.16.1  Prevent a crash if the query tool is closed whilst a
  file is loading [Akshay Joshi]
    2012-10-09 AV  1.16.1  Fix setting of comments on PPAS procedures.
    2012-10-08 DP  1.16.1  Don't autosize the search results columns if no
  results are found [Akshay Joshi]
    2012-10-08 AV  1.16.1  Prevent a crash if opening a second config file in
  the editor.
    2012-10-08 DP  1.16.1  Prevent the SSL options combo box displaying
  duplicate options if the server dialogue is
  reopened [Akshay Joshi]
    2012-09-14 GL  1.16.1  Fix trigger query when connected to PostgreSQL 8.2 or
  lower, per a report from Jon Roberts.
    2012-09-12 GL  1.16.1  Fix message when executing an empty query, per Marc
  Mamin.
    2012-05-08 GL  1.16.0  Add privilege support on aggregates.
    2012-05-05 GL  1.16.0  Add inline function support on languages.
    2012-04-29 GL  1.16.0  Add support for range types.
    2012-04-28 GL  1.16.0  Add support for setting db/user config on dlgRole.
    2012-04-08 GL  1.16.0  Move references table textbox to the third tab in
  dlgForeignKey. Per request from Colin Beckingham.
    2012-04-05 GL  1.16.0  Support for the new two columns in 9.2 pg_stat_database
    2012-03-12 GL  1.16.0  Support for renaming constraints (9.2).
    2012-03-02 GL  1.16.0  Fix wxWidgets 2.9 compatibility with pgAdmin on Linux
  [Akshay Joshi].
    2012-02-23 GL  1.16.0  New import tool.
    2012-02-15 GL  1.16.0  Support for the LEAKPROOF option in functions.
    2012-02-13 GL  1.16.0  Support ANALYZE, CATEGORY, and PREFERED items for
  CREATE TYPE statement.
    2012-02-11 GL  1.16.0  Support CREATE TABLE LIKE.
    2012-02-09 GL  1.16.0  Support for the new TIMING option in EXPLAIN ANALYZE.
    2012-01-26 GL  1.16.0  Support for the new three columns in 9.2 pg_stat_database
    2012-01-22 GL  1.16.0  Use date_trunc to skip the microseconds part of all
  timestamp fields in frmStatus.
    2012-01-22 GL  1.16.0  Support new/changed pg_stat_activity fields.
    2012-01-08 GL  1.16.0  Allow renaming a domain.
    2012-01-07 GL  1.16.0  Add subitems to the schemas and catalogs in GQB.
  Request from Colin Beckingham.
    2012-01-05 GL  1.16.0  Support section options for pg_dump/pg_restore.
    2012-01-03 GL  1.16.0  Add security_barrier option handling for views.
    2011-12-19 DP  1.16.0  Add an "New Folder" button to the "Add Favourite" dialog
  in the query tool [Dhiraj Chawla]
    2011-12-12 GL  1.16.0  Support for the new sslcompression connection option.
    2011-12-11 GL  1.16.0  Add renaming of FDW and Server objects.
    2011-12-10 GL  1.16.0  Support for TRUNCATE permission
    2011-09-10 GL  1.16.0  Reverse engineering in the database designer.
  Patch from Luis Ochoa with some fixes by me.
    2011-09-04 GL  1.16.0  Highlight the other brace even if the current one is
  before the caret (request from Andreas).
    2011-08-24 DP  1.16.0  Add options to refresh objects automatically when
  clicked [Vinicius Santos]
    2011-08-15 GL  1.16.0  Redesign frmOptions.
    2011-08-11 GL  1.16.0  Prevents dropping connection, dropping or refreshing
  object when a properties dialog is open.
    2011-08-11 GL  1.16.0  Support for multimodels diagram in the database
  designer. Patch from Luis Ochoa with some fixes by me.
    2011-08-07 GL  1.16.0  Implement enable/disable save button, on text change.
  Patch from Vinicius Santos.
    2011-07-25 GL  1.16.0  Change doc build system.
    2011-07-25 GL  1.16.0  Support for security labels on global/shared objects
  (9.2 feature).
    2011-07-25 GL  1.16.0  Support for security labels on local objects (9.1
  feature).
    2011-07-25 GL  1.16.0  Support for non valid domains, and check constraints
  (9.2 feature).
    2011-07-25 GL  1.16.0  Add load/save support for the Database Designer. Patch
  from Luis Ochoa.
    2011-07-09 GL  1.16.0  Allow change of schema in the UI. Patch from Thom
  Brown.
    2011-07-05 GL  1.16.0  Add "Search Objects" dialog. Patch from Jasmin Dizdarevic.
    2011-07-03 GL  1.16.0  New maintenance action: CLUSTER. Patch from Thom Brown.
    2011-07-02 GL  1.16.0  Enable "Has OIDs" on 8.4+ even when the table is
  already created. Patch from Thom Brown.
    2011-06-27 GL  1.16.0  Add Database Designer. Patch from Luis Ochoa.
    2011-06-23 DP  1.16.0  Allow change of the fill factor. Patch from Thom Brown.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1382184000">- spec remove cleaning png2c (fixed in 1.18)
- update to 1.18.1
  http://www.pgadmin.org/development/changelog.php
  Date       Dev Ver     Change details
  - --------- --- ------  --------------
  2013-09-29 GL  1.18.1  Allow the dump of pg&lt;something&gt; schemas.
  2013-09-26 DP  1.18.1  Prevent a crash on Windows when dropping a column or a
  constraint on a table [Dhiraj Chawla]
  2013-09-26 DP  1.18.1  Ensure DDLScript will work with Slony 2.2+ which has a
  new SQL level API [Neel Patel]
  2013-09-26 DP  1.18.1  Fix ordering of object types in the display options and
  add Event Triggers which were missing [Dhiraj Chawla].
  2013-09-21 AV  1.18.1  Ensure the debugger can cope with functions that have an
  OUT parameter as the first.
  2013-09-19 DP  1.18.1  Fix the quoting of user mapping objects [Dinesh Kumar]
  2013-09-19 DP  1.18.1  Ensure that materialised views are available as targets
  for synonyms [Neel Patel]
  2013-09-19 DP  1.18.1  Fix the query used to find tables in a Slony
  replication set [Neel Patel]
  2013-09-11 DP  1.18.1  Prevent a crash if a user starts an external process
  such as a backup, and then immediately hits cancel
  [Neel Patel].
  2013-09-06 DP  1.18.1  Fix a memory leak in the Event Trigger code [Dinesh
  Kumar].
  2013-08-20 AV  1.18.0  Fix a layout bug in the graphical explain renderer that
  could render nodes on top of each other.
  2013-08-06 DP  1.18.0  Fix Slony's DDL Script support [Akshay Joshi].
  2013-07-26 DP  1.18.0  Add support for Event Triggers in 9.3+ [Dinesh Kumar].
  2013-07-22 DP  1.18.0  Avoid using a Help cache file that needs to be world
  writeable, and ensure sed is happy when post-processing
  helpfiles.
  2013-07-22 DP  1.18.0  Fix the help path on the import dialogue and improve the
  error handling [Akshay Joshi].
  2013-07-22 DP  1.18.0  Fix path the the Search Objects help doc [Dhiraj Chawla].
  2013-07-18 GL  1.18.0  Fix UTF-8 display for guru hints [Marek Cernocky].
  2013-07-08 DP  1.18.0  Prevent a crash when creating a stored procedure in
  PPAS [Dinesh Kumar].
  2013-06-19 GL  1.18.0  Disable the Favourites menu items if there is no
  favourites file path (per a comment from Michael Shapiro).
  2013-06-18 GL  1.18.0  Make No the default button on the Truncate confirmation
  dialog (per request from Humberto Cereser Ibanez).
  2013-06-18 DP  1.18.0  Support Materialized Views [Neel Patel].
  2013-06-07 DP  1.18.0  Avoid a possible crash on Linux when using the
  "Script" options of the Query Tool [aditsu].
  2013-05-26 DP  1.18.0  Fix comments on constraints [Thom Brown].
  2013-05-26 DP  1.18.0  Fix schema prefixes in cast definitions in the browser.
  2013-05-26 DP  1.18.0  Treat sequences as first class objects in the Grant
  Wizard. Support USAGE and remove obsolete RULE
  permissions [Dhiraj Chawla].
  2013-05-26 DP  1.18.0  Set the default backup type to "Custom".
  2013-05-21 DP  1.18.0  Improve the copy handling on the Edit Grid so that
  it works more consistently and predictably.
  2013-05-20 DP  1.18.0  Fix comments on columns.
  2013-05-20 DP  1.18.0  Remove the "Apply" buttons from the function, view
  package and external table dialogues. Their use is
  discouraged, and the code is fragile, complex and
  very buggy.
  2013-05-20 DP  1.18.0  Fix a crash that could occur if the browser fails to
  detect that an object has been changed by another
  session.
  2013-05-17 DP  1.18.0  Change the default SQL box font to a slightly smaller
  size on GTK based platforms.
  2013-05-17 DP  1.18.0  Don't prompt the user for a password if they're using
  a client certificate.
  2013-05-17 DP  1.18.0  Ensure global backups use the mintenance database to
  avoid access issue with postgres or template1.
  2013-05-17 DP  1.18.0  Fix SSL certificate authentication.
  2013-05-08 DP  1.18.0  Fix renaming and schema changes for stored procedures
  in PPAS [Dinesh Kumar].
  2013-05-02 DP  1.18.0  Add SSH tunnelling support to allow connections to be
  made to hosts via an SSH server [Akshay Joshi].
  2013-05-02 DP  1.18.0  Display the index validity in the properties list for
  indexes and index-based constraints [Gabrielle Roth].
  2013-04-29 DP  1.18.0  Add an option to include column headers when copying
  from the query tool results [Jasmin Dizdarevic].
  2013-04-29 DP  1.18.0  Allow the decimal mark displayed by the query tool to be
  configured as the thousands separator can [Jasmin
  Dizdarevic].
  2013-04-25 DP  1.18.0  Ensure the Query Tool's maximum column length setting
  is honoured.
  2013-04-22 DP  1.18.0  Handle default privileges to PUBLIC correctly. [Dhiraj
  Chawla].
  2013-03-24 GL  1.18.0  Add tab option in the Import dialog. Per a request from
  Jeff Janes.
  2013-03-17 GL  1.18.0  Add smallserial handling. Per a request from Matthew
  Syphus.
  2013-03-01 DP  1.18.0  Fix the editing of pg_hba.conf files [Dhiraj Chawla].
  2013-02-25 DP  1.18.0  Fix the display of extension owner names.
  2013-02-23 GL  1.18.0  Add a title to the backup and restore windows. Per
  request from Bastiaan Olij.
  2013-02-22 DP  1.18.0  Fix a bug that could cause a NOTICE to be displayed
  when rendering FTS Configurations in the tree.
  2013-02-07 DP  1.18.0  Don't try to display dependents or dependencies for
  pgAgent jobs, schedules or steps.
  2013-02-06 DP  1.18.0  Fix the handling of expiry times when modifying roles.
  2013-02-04 DP  1.18.0  Prevent foreign keys being recreated unnecessarily when
  modifying tables [Michael Banck]
  2013-01-24 DP  1.18.0  Prevent Cmd+S adding characters to the Query Tool when
  the Save button is disabled.
  2013-01-18 DP  1.18.0  Fix handling of Greenplum partitions [Lubomir Petrov]
  2013-01-06 GL  1.18.0  Add -V/--version CLI option.
  2013-01-06 GL  1.18.0  Add actions menu to the serverstatus tool.
  2013-01-06 GL  1.18.0  Fix the database SQL when reseting a configuration
  parameter. Per a report from Bartosz Dmytrak.
  2013-01-04 GL  1.18.0  Refresh the toolbar buttons when a list has been
  updated. Per a report from Evan Martin.
  2013-01-04 GL  1.18.0  Fix the "NO INHERIT" query. Report from Thomas Joseph.
  2012-12-24 GL  1.18.0  Display default privs. Report from Nathan Alden.
  2012-12-24 GL  1.18.0  Sort references by schema name and relation name in
  dlgForeignKey. Report from Michal Kozusznik.
  2012-12-24 GL  1.18.0  Fix the change of the superuser attribute. Report from
  Michal Kozusznik.
  2012-12-18 DP  1.18.0  Prevent a crash when using Cmd-A on a file loaded into
  the Query Tool when opened with Cmd-E on Mac.
  2012-12-07 DP  1.18.0  Fix the queries used to get object comments to allow
  for duplicate OIDs that may be present following use
  of pg_upgrade.</changelog>
  <changelog author="max@suse.com" date="1386849600">- Remove broken and unneeded dependency on libecpg (bnc#854754).</changelog>
  <changelog author="termim@gmail.com" date="1422446400">- update to 1.20.0
  * Resolving the inconsistency of preservation of modified
    information of the columns, while adding/editing a table from
    the table dialog
  * Add missing nodes to graphical explain plan
  * Fix the Resource Groups dialog - separated the statements,
    which can not be ran in single transaction
  * Support for Slony-I 2.2+ with PostgreSQL 9.3+
  * Support smallserial columns in Edit Data Window
  * Restore the user specified size on the grid (which contains the
    result) in Query windows to fix an issue related to the column
    size is too narrow on subsequent Explain execution
  * Empty the Undo/Redo history everytime new file is opened
  * Added accelerator F8 for 'Execute to file' in the Query window
  * Beautify the query shown in the SQL pane for the functions
    having multiple arguments by adding new lines with small
    modification
  * Check for the columnlist for the UPDATE OF syntax on trigger
    also works with PPAS 9.5+
  * Proper saving of columns width in the server status window
  * CHECK OPTION is applicable to the views only, and not the
    materialized views
  * Prevent a crash during the update of the macro or favourite
    list
  * Allow quick injectection of favourites by name
  * Fix handling of saving macros after pasting a query in the box
  * Fix handling of char()[] columns in the Edit Grid
  * Support the new check_option parameter of views
  * Handle the 9.4 MOVE clause of ALTER TABLESPACE
  * Add a new action menu to refresh a materialized view
  * Support the new 9.4 columns in pg_stat_activity
  * Save search options for next time
  * Ensure Favourite queries are only saved when the OK button is
    pressed
  * Fix an issue refreshing functions in PPAS packages
  * Improve handling of lost connections
  * Allow searching for database objects by comment and definition
    content
  * Add support for Resource Groups in PPAS 9.4
  * Add Save and Exit shortcut keys to the edit grid
  * Enable backward search in SQL Box using Shift + F3
  * Allow more flexible selection/deselection of rows and columns
    in Edit Grid
  * Allow more options with the plain backup.
  * Use a much smarter auto-sizing algorithm for the columns in the
    Query Tool output grid.
  * Remember the last panel used on the Options dialogue, and
    display the default panel if a group node is selected on the
    tree
  * Allow parallel dump with -j starting with 9.3
- update to 1.18.2
  * Fix SQL for GRANT on a sequence. Report from liuyuanyuan.
  * Fix escape handling in pgpass files
  * GQB forgot the materialized views.
  * Don't set log_min_messages from the debugger
  * Fix a crash on OSX when run explain through shortcut in query
    editor, when mouse is over a existing shape, and popup, showing
    the step information, is on
  * Using the GetOid() function instead of GetLong() for Oid
    columns
  * Fix SQL comments for inherited columns.
  * Flush the changes in the settings as soon as new server is
    added
  * Don't include obsolete config settings from &lt;= 8.3 in the
    config editor unless running on an appropriate server.
  * Ensure the Type dialogue detects name changes.
  * Ensure report titles don't overflow the page width
  * Ensure reports overflow the page width properly
  * Add missing "port" option for SSH tunnels.
  * Set 32bit PostgreSQL, EnterpriseDB PATH (in case - 64bit
    respective applications not found, and 32bit(s) are available)
    for 64bit pgAdmin III.
  * Improved the debugger to work better with PPAS &lt;= 9.2
  * Fix the handling of the "Valid Until" date/time on the role
    dialogue on Mac.</changelog>
  <changelog author="mpluskal@suse.com" date="1439380800">- Add explicit dependencies on autoconf and libtool</changelog>
  <changelog author="jweberhofer@weberhofer.at" date="1444996800">- Do not recommend but only suggest to install postgresql-server.</changelog>
  <changelog author="termim@gmail.com" date="1453809600">- update to 1.22.0
  * Resolved an issue related to check options selection in the view
    properties dialog with the check option.
  * Merged the libssh2 to the latest version.
  * Properly detect serial columns as such when identifiers have been
    truncated.
  * Fixes an issue related to the column inheritance information properly,
    when one (or, more) common columns are inherited from multiple tables.
  * Ensure the correct syntax used for moving the objects from one
    tablespace to another.
  * Ensure the correct line endings are used when copying from the SQL Pane
  * Toolbar icons, and menu items for Commit and Rollback actions.
  * Display the connection details for the current browser object in the
    status bar
  * Fixed an issue related to different menus enabling in the Query Tool on
    Ubunutu unity.
  * Reset the position (x, y) for dialog(s), and frame(s) to 0 (if found
    negative), while saving its position and size.
  * Fixes an issue identifying the return type to TABLE in some cases,
    using pg_get_function_result(..) for the same instead of format_type(..)
  * Honour PGPASSFILE environment variable for saving, retrieving the
    password instead of always works with pgpass.conf (on windows)/.pgpass
    (on non-windows)
  * Fix a segfault occurs while detecting transaction section requirement,
    when autocommit has been disabled.
  * Format execution time in a more readable manner
  * Improve sorting in Data editor
  * Allow to format the selecte SQL using external tools in Query Editor
  * Allow to set auto-commit mode to on/off in the query editor
  * Do not try unlock the mutex, which was not owned by the thread, while
    creating the popup menu
  * Set the focus on browser tree windows on startup
  * Make the arrow key navigation consistent across all platform on the
    object browser tree
  * Show indexes for the materialized views in Query pane
  * Add support for searching materialized views in the</changelog>
  <changelog author="crrodriguez@opensuse.org" date="1456660800">- remove obsolete suse_version checks
- fix debuginfo generation.</changelog>
  <changelog author="crrodriguez@opensuse.org" date="1456660801">- Update to version 1.22.1
  * Don't barf when connecting to Greenplum or Greenplum HAWQ
  * Fix selection of conversion functions in the CREATE CONVERSION dialogue.
  * Properly quote type names in the Type dialogue, andensure range
  information is displayed for existing types
  * Fix selection of cast functions in the Cast dialogue</changelog>
  <changelog author="martin.liska@suse.com" date="1467374400">- Add -fno-delete-null-pointer-checks to CXXFLAGS to workaround
  boo#986857.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to version 1.22.2
  * Include the Negator when reverse engineering SQL for operators
  * Fix the psql plugin command on OSX to work more reliably
  * Prevent a crash in some situtions where the database connection
  is lost and needs to be reset.
  * Fix display of elapsed query time for queries running longer than
  1 hour
- This is the final release of pgadmin3</changelog>
  <changelog author="bruno@ioda-net.ch" date="1485691200">- Packaging :
  + spec-clean minimal
  + remove obsolete version sle and openSUSE
  + globalize \r removal in css files
  + use wxWidgets-3_0-nostl-devel to remove dependency of gst 0.10
    so use internal dependency generator on openSUSE &gt; 1315
  + Add WX_VER variable to build correctly
  + Added patch wxWidget-limit-libs-used.patch to explicitely add
    the needed libs.
  + Try to handle differents WX versions between openSUSE and SLE</changelog>
  <changelog author="bruno@ioda-net.ch" date="1492516800">- Add 0001-Set-row-heights-based-on-pixels-rather-than-points.patch
  Fix control grid row on hidpi screen.</changelog>
</package>
<package pkgid="77971d83b0af4b874c0180485d386d65a6c148db93d0b13870e3bd9e5fdafaed" name="pgadmin3-debugsource" arch="x86_64">
  <version epoch="0" ver="1.22.2" rel="39.4"/>
  <changelog author="saschpe@gmx.de" date="1296734400">- added dependency on wxWidgets for openSUSE-11.4 and greater</changelog>
  <changelog author="mrueckert@suse.de" date="1298980800">- use wx_requires on 11.4 and newer</changelog>
  <changelog author="klaussfreire@gmail.com" date="1301313600">- update to upstream git 2011-03-28</changelog>
  <changelog author="saschpe@suse.de" date="1302523200">- set license to 'PostgreSQL', fixes bnc#675943</changelog>
  <changelog author="klaussfreire@gmail.com" date="1316174400">- update to upstream 1.14.0
  * see http://www.pgadmin.org/development/changelog.php</changelog>
  <changelog author="coolo@suse.com" date="1322827200">- add automake as buildrequire to avoid implicit dependency</changelog>
  <changelog author="pascal.bleser@opensuse.org" date="1340539200">- update to 1.14.3:
  http://www.pgadmin.org/development/changelog.php</changelog>
  <changelog author="bruno@ioda-net.ch" date="1359374400">- fix bnc#800831
- update to 1.16.1
  http://www.pgadmin.org/development/changelog.php
    Date       Dev Ver     Change details
  - --------- --- ------  --------------
    2012-12-03 DP  1.16.1  Prevent a crash that could happen if further changes
  were made on a dialogue after using the Apply button.
  [Akshay Joshi]
    2012-11-29 GL  1.16.1  Save new comments on already existing columns when
  editing a table. Per a report from Jeff Janes.
    2012-11-29 GL  1.16.1  Fix the query editor behaviour when executing COPY TO
  stdout and COPY FROM stdin [Heikki Linnakangas]
    2012-11-28 AV  1.16.1  Date picker controls returns a full timestamp by
  default, which can cause inadvertent date changes
  on jobs and role validty dates. Ignore the time part.
    2012-11-26 MH  1.16.1  Fix query for database descriptions
    2012-11-15 DP  1.16.1  Avoid querying the catalogs for toast table settings
  for every table in the database. This gives a huge
  performance gain with large schemas.
    2012-11-08 DP  1.16.1  Prevent a crash when refreshing a node which has a
  child with an open dialogue [Dhiraj Chawla]
    2012-11-08 DP  1.16.1  Fix dropping/renaming of indexes [Akshay Joshi]
    2012-11-08 DP  1.16.1  Avoid updating the GQB model on every key press in
  the query tool [Dhiraj Chawla]
    2012-11-02 DP  1.16.1  Fix a crash that can occur when renaming objects.
  [Ashesh Vashi/Sachin Srivastava]
    2012-11-01 DP  1.16.1  Fix dropping of constraints [Akshay Joshi]
    2012-10-31 DP  1.16.1  Fix the "blocked by" column in the server status
  dialogue on 9.2 servers [Sachin Srivastava]
    2012-10-11 DP  1.16.1  Prevent a crash if the query tool is closed whilst a
  file is loading [Akshay Joshi]
    2012-10-09 AV  1.16.1  Fix setting of comments on PPAS procedures.
    2012-10-08 DP  1.16.1  Don't autosize the search results columns if no
  results are found [Akshay Joshi]
    2012-10-08 AV  1.16.1  Prevent a crash if opening a second config file in
  the editor.
    2012-10-08 DP  1.16.1  Prevent the SSL options combo box displaying
  duplicate options if the server dialogue is
  reopened [Akshay Joshi]
    2012-09-14 GL  1.16.1  Fix trigger query when connected to PostgreSQL 8.2 or
  lower, per a report from Jon Roberts.
    2012-09-12 GL  1.16.1  Fix message when executing an empty query, per Marc
  Mamin.
    2012-05-08 GL  1.16.0  Add privilege support on aggregates.
    2012-05-05 GL  1.16.0  Add inline function support on languages.
    2012-04-29 GL  1.16.0  Add support for range types.
    2012-04-28 GL  1.16.0  Add support for setting db/user config on dlgRole.
    2012-04-08 GL  1.16.0  Move references table textbox to the third tab in
  dlgForeignKey. Per request from Colin Beckingham.
    2012-04-05 GL  1.16.0  Support for the new two columns in 9.2 pg_stat_database
    2012-03-12 GL  1.16.0  Support for renaming constraints (9.2).
    2012-03-02 GL  1.16.0  Fix wxWidgets 2.9 compatibility with pgAdmin on Linux
  [Akshay Joshi].
    2012-02-23 GL  1.16.0  New import tool.
    2012-02-15 GL  1.16.0  Support for the LEAKPROOF option in functions.
    2012-02-13 GL  1.16.0  Support ANALYZE, CATEGORY, and PREFERED items for
  CREATE TYPE statement.
    2012-02-11 GL  1.16.0  Support CREATE TABLE LIKE.
    2012-02-09 GL  1.16.0  Support for the new TIMING option in EXPLAIN ANALYZE.
    2012-01-26 GL  1.16.0  Support for the new three columns in 9.2 pg_stat_database
    2012-01-22 GL  1.16.0  Use date_trunc to skip the microseconds part of all
  timestamp fields in frmStatus.
    2012-01-22 GL  1.16.0  Support new/changed pg_stat_activity fields.
    2012-01-08 GL  1.16.0  Allow renaming a domain.
    2012-01-07 GL  1.16.0  Add subitems to the schemas and catalogs in GQB.
  Request from Colin Beckingham.
    2012-01-05 GL  1.16.0  Support section options for pg_dump/pg_restore.
    2012-01-03 GL  1.16.0  Add security_barrier option handling for views.
    2011-12-19 DP  1.16.0  Add an "New Folder" button to the "Add Favourite" dialog
  in the query tool [Dhiraj Chawla]
    2011-12-12 GL  1.16.0  Support for the new sslcompression connection option.
    2011-12-11 GL  1.16.0  Add renaming of FDW and Server objects.
    2011-12-10 GL  1.16.0  Support for TRUNCATE permission
    2011-09-10 GL  1.16.0  Reverse engineering in the database designer.
  Patch from Luis Ochoa with some fixes by me.
    2011-09-04 GL  1.16.0  Highlight the other brace even if the current one is
  before the caret (request from Andreas).
    2011-08-24 DP  1.16.0  Add options to refresh objects automatically when
  clicked [Vinicius Santos]
    2011-08-15 GL  1.16.0  Redesign frmOptions.
    2011-08-11 GL  1.16.0  Prevents dropping connection, dropping or refreshing
  object when a properties dialog is open.
    2011-08-11 GL  1.16.0  Support for multimodels diagram in the database
  designer. Patch from Luis Ochoa with some fixes by me.
    2011-08-07 GL  1.16.0  Implement enable/disable save button, on text change.
  Patch from Vinicius Santos.
    2011-07-25 GL  1.16.0  Change doc build system.
    2011-07-25 GL  1.16.0  Support for security labels on global/shared objects
  (9.2 feature).
    2011-07-25 GL  1.16.0  Support for security labels on local objects (9.1
  feature).
    2011-07-25 GL  1.16.0  Support for non valid domains, and check constraints
  (9.2 feature).
    2011-07-25 GL  1.16.0  Add load/save support for the Database Designer. Patch
  from Luis Ochoa.
    2011-07-09 GL  1.16.0  Allow change of schema in the UI. Patch from Thom
  Brown.
    2011-07-05 GL  1.16.0  Add "Search Objects" dialog. Patch from Jasmin Dizdarevic.
    2011-07-03 GL  1.16.0  New maintenance action: CLUSTER. Patch from Thom Brown.
    2011-07-02 GL  1.16.0  Enable "Has OIDs" on 8.4+ even when the table is
  already created. Patch from Thom Brown.
    2011-06-27 GL  1.16.0  Add Database Designer. Patch from Luis Ochoa.
    2011-06-23 DP  1.16.0  Allow change of the fill factor. Patch from Thom Brown.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1382184000">- spec remove cleaning png2c (fixed in 1.18)
- update to 1.18.1
  http://www.pgadmin.org/development/changelog.php
  Date       Dev Ver     Change details
  - --------- --- ------  --------------
  2013-09-29 GL  1.18.1  Allow the dump of pg&lt;something&gt; schemas.
  2013-09-26 DP  1.18.1  Prevent a crash on Windows when dropping a column or a
  constraint on a table [Dhiraj Chawla]
  2013-09-26 DP  1.18.1  Ensure DDLScript will work with Slony 2.2+ which has a
  new SQL level API [Neel Patel]
  2013-09-26 DP  1.18.1  Fix ordering of object types in the display options and
  add Event Triggers which were missing [Dhiraj Chawla].
  2013-09-21 AV  1.18.1  Ensure the debugger can cope with functions that have an
  OUT parameter as the first.
  2013-09-19 DP  1.18.1  Fix the quoting of user mapping objects [Dinesh Kumar]
  2013-09-19 DP  1.18.1  Ensure that materialised views are available as targets
  for synonyms [Neel Patel]
  2013-09-19 DP  1.18.1  Fix the query used to find tables in a Slony
  replication set [Neel Patel]
  2013-09-11 DP  1.18.1  Prevent a crash if a user starts an external process
  such as a backup, and then immediately hits cancel
  [Neel Patel].
  2013-09-06 DP  1.18.1  Fix a memory leak in the Event Trigger code [Dinesh
  Kumar].
  2013-08-20 AV  1.18.0  Fix a layout bug in the graphical explain renderer that
  could render nodes on top of each other.
  2013-08-06 DP  1.18.0  Fix Slony's DDL Script support [Akshay Joshi].
  2013-07-26 DP  1.18.0  Add support for Event Triggers in 9.3+ [Dinesh Kumar].
  2013-07-22 DP  1.18.0  Avoid using a Help cache file that needs to be world
  writeable, and ensure sed is happy when post-processing
  helpfiles.
  2013-07-22 DP  1.18.0  Fix the help path on the import dialogue and improve the
  error handling [Akshay Joshi].
  2013-07-22 DP  1.18.0  Fix path the the Search Objects help doc [Dhiraj Chawla].
  2013-07-18 GL  1.18.0  Fix UTF-8 display for guru hints [Marek Cernocky].
  2013-07-08 DP  1.18.0  Prevent a crash when creating a stored procedure in
  PPAS [Dinesh Kumar].
  2013-06-19 GL  1.18.0  Disable the Favourites menu items if there is no
  favourites file path (per a comment from Michael Shapiro).
  2013-06-18 GL  1.18.0  Make No the default button on the Truncate confirmation
  dialog (per request from Humberto Cereser Ibanez).
  2013-06-18 DP  1.18.0  Support Materialized Views [Neel Patel].
  2013-06-07 DP  1.18.0  Avoid a possible crash on Linux when using the
  "Script" options of the Query Tool [aditsu].
  2013-05-26 DP  1.18.0  Fix comments on constraints [Thom Brown].
  2013-05-26 DP  1.18.0  Fix schema prefixes in cast definitions in the browser.
  2013-05-26 DP  1.18.0  Treat sequences as first class objects in the Grant
  Wizard. Support USAGE and remove obsolete RULE
  permissions [Dhiraj Chawla].
  2013-05-26 DP  1.18.0  Set the default backup type to "Custom".
  2013-05-21 DP  1.18.0  Improve the copy handling on the Edit Grid so that
  it works more consistently and predictably.
  2013-05-20 DP  1.18.0  Fix comments on columns.
  2013-05-20 DP  1.18.0  Remove the "Apply" buttons from the function, view
  package and external table dialogues. Their use is
  discouraged, and the code is fragile, complex and
  very buggy.
  2013-05-20 DP  1.18.0  Fix a crash that could occur if the browser fails to
  detect that an object has been changed by another
  session.
  2013-05-17 DP  1.18.0  Change the default SQL box font to a slightly smaller
  size on GTK based platforms.
  2013-05-17 DP  1.18.0  Don't prompt the user for a password if they're using
  a client certificate.
  2013-05-17 DP  1.18.0  Ensure global backups use the mintenance database to
  avoid access issue with postgres or template1.
  2013-05-17 DP  1.18.0  Fix SSL certificate authentication.
  2013-05-08 DP  1.18.0  Fix renaming and schema changes for stored procedures
  in PPAS [Dinesh Kumar].
  2013-05-02 DP  1.18.0  Add SSH tunnelling support to allow connections to be
  made to hosts via an SSH server [Akshay Joshi].
  2013-05-02 DP  1.18.0  Display the index validity in the properties list for
  indexes and index-based constraints [Gabrielle Roth].
  2013-04-29 DP  1.18.0  Add an option to include column headers when copying
  from the query tool results [Jasmin Dizdarevic].
  2013-04-29 DP  1.18.0  Allow the decimal mark displayed by the query tool to be
  configured as the thousands separator can [Jasmin
  Dizdarevic].
  2013-04-25 DP  1.18.0  Ensure the Query Tool's maximum column length setting
  is honoured.
  2013-04-22 DP  1.18.0  Handle default privileges to PUBLIC correctly. [Dhiraj
  Chawla].
  2013-03-24 GL  1.18.0  Add tab option in the Import dialog. Per a request from
  Jeff Janes.
  2013-03-17 GL  1.18.0  Add smallserial handling. Per a request from Matthew
  Syphus.
  2013-03-01 DP  1.18.0  Fix the editing of pg_hba.conf files [Dhiraj Chawla].
  2013-02-25 DP  1.18.0  Fix the display of extension owner names.
  2013-02-23 GL  1.18.0  Add a title to the backup and restore windows. Per
  request from Bastiaan Olij.
  2013-02-22 DP  1.18.0  Fix a bug that could cause a NOTICE to be displayed
  when rendering FTS Configurations in the tree.
  2013-02-07 DP  1.18.0  Don't try to display dependents or dependencies for
  pgAgent jobs, schedules or steps.
  2013-02-06 DP  1.18.0  Fix the handling of expiry times when modifying roles.
  2013-02-04 DP  1.18.0  Prevent foreign keys being recreated unnecessarily when
  modifying tables [Michael Banck]
  2013-01-24 DP  1.18.0  Prevent Cmd+S adding characters to the Query Tool when
  the Save button is disabled.
  2013-01-18 DP  1.18.0  Fix handling of Greenplum partitions [Lubomir Petrov]
  2013-01-06 GL  1.18.0  Add -V/--version CLI option.
  2013-01-06 GL  1.18.0  Add actions menu to the serverstatus tool.
  2013-01-06 GL  1.18.0  Fix the database SQL when reseting a configuration
  parameter. Per a report from Bartosz Dmytrak.
  2013-01-04 GL  1.18.0  Refresh the toolbar buttons when a list has been
  updated. Per a report from Evan Martin.
  2013-01-04 GL  1.18.0  Fix the "NO INHERIT" query. Report from Thomas Joseph.
  2012-12-24 GL  1.18.0  Display default privs. Report from Nathan Alden.
  2012-12-24 GL  1.18.0  Sort references by schema name and relation name in
  dlgForeignKey. Report from Michal Kozusznik.
  2012-12-24 GL  1.18.0  Fix the change of the superuser attribute. Report from
  Michal Kozusznik.
  2012-12-18 DP  1.18.0  Prevent a crash when using Cmd-A on a file loaded into
  the Query Tool when opened with Cmd-E on Mac.
  2012-12-07 DP  1.18.0  Fix the queries used to get object comments to allow
  for duplicate OIDs that may be present following use
  of pg_upgrade.</changelog>
  <changelog author="max@suse.com" date="1386849600">- Remove broken and unneeded dependency on libecpg (bnc#854754).</changelog>
  <changelog author="termim@gmail.com" date="1422446400">- update to 1.20.0
  * Resolving the inconsistency of preservation of modified
    information of the columns, while adding/editing a table from
    the table dialog
  * Add missing nodes to graphical explain plan
  * Fix the Resource Groups dialog - separated the statements,
    which can not be ran in single transaction
  * Support for Slony-I 2.2+ with PostgreSQL 9.3+
  * Support smallserial columns in Edit Data Window
  * Restore the user specified size on the grid (which contains the
    result) in Query windows to fix an issue related to the column
    size is too narrow on subsequent Explain execution
  * Empty the Undo/Redo history everytime new file is opened
  * Added accelerator F8 for 'Execute to file' in the Query window
  * Beautify the query shown in the SQL pane for the functions
    having multiple arguments by adding new lines with small
    modification
  * Check for the columnlist for the UPDATE OF syntax on trigger
    also works with PPAS 9.5+
  * Proper saving of columns width in the server status window
  * CHECK OPTION is applicable to the views only, and not the
    materialized views
  * Prevent a crash during the update of the macro or favourite
    list
  * Allow quick injectection of favourites by name
  * Fix handling of saving macros after pasting a query in the box
  * Fix handling of char()[] columns in the Edit Grid
  * Support the new check_option parameter of views
  * Handle the 9.4 MOVE clause of ALTER TABLESPACE
  * Add a new action menu to refresh a materialized view
  * Support the new 9.4 columns in pg_stat_activity
  * Save search options for next time
  * Ensure Favourite queries are only saved when the OK button is
    pressed
  * Fix an issue refreshing functions in PPAS packages
  * Improve handling of lost connections
  * Allow searching for database objects by comment and definition
    content
  * Add support for Resource Groups in PPAS 9.4
  * Add Save and Exit shortcut keys to the edit grid
  * Enable backward search in SQL Box using Shift + F3
  * Allow more flexible selection/deselection of rows and columns
    in Edit Grid
  * Allow more options with the plain backup.
  * Use a much smarter auto-sizing algorithm for the columns in the
    Query Tool output grid.
  * Remember the last panel used on the Options dialogue, and
    display the default panel if a group node is selected on the
    tree
  * Allow parallel dump with -j starting with 9.3
- update to 1.18.2
  * Fix SQL for GRANT on a sequence. Report from liuyuanyuan.
  * Fix escape handling in pgpass files
  * GQB forgot the materialized views.
  * Don't set log_min_messages from the debugger
  * Fix a crash on OSX when run explain through shortcut in query
    editor, when mouse is over a existing shape, and popup, showing
    the step information, is on
  * Using the GetOid() function instead of GetLong() for Oid
    columns
  * Fix SQL comments for inherited columns.
  * Flush the changes in the settings as soon as new server is
    added
  * Don't include obsolete config settings from &lt;= 8.3 in the
    config editor unless running on an appropriate server.
  * Ensure the Type dialogue detects name changes.
  * Ensure report titles don't overflow the page width
  * Ensure reports overflow the page width properly
  * Add missing "port" option for SSH tunnels.
  * Set 32bit PostgreSQL, EnterpriseDB PATH (in case - 64bit
    respective applications not found, and 32bit(s) are available)
    for 64bit pgAdmin III.
  * Improved the debugger to work better with PPAS &lt;= 9.2
  * Fix the handling of the "Valid Until" date/time on the role
    dialogue on Mac.</changelog>
  <changelog author="mpluskal@suse.com" date="1439380800">- Add explicit dependencies on autoconf and libtool</changelog>
  <changelog author="jweberhofer@weberhofer.at" date="1444996800">- Do not recommend but only suggest to install postgresql-server.</changelog>
  <changelog author="termim@gmail.com" date="1453809600">- update to 1.22.0
  * Resolved an issue related to check options selection in the view
    properties dialog with the check option.
  * Merged the libssh2 to the latest version.
  * Properly detect serial columns as such when identifiers have been
    truncated.
  * Fixes an issue related to the column inheritance information properly,
    when one (or, more) common columns are inherited from multiple tables.
  * Ensure the correct syntax used for moving the objects from one
    tablespace to another.
  * Ensure the correct line endings are used when copying from the SQL Pane
  * Toolbar icons, and menu items for Commit and Rollback actions.
  * Display the connection details for the current browser object in the
    status bar
  * Fixed an issue related to different menus enabling in the Query Tool on
    Ubunutu unity.
  * Reset the position (x, y) for dialog(s), and frame(s) to 0 (if found
    negative), while saving its position and size.
  * Fixes an issue identifying the return type to TABLE in some cases,
    using pg_get_function_result(..) for the same instead of format_type(..)
  * Honour PGPASSFILE environment variable for saving, retrieving the
    password instead of always works with pgpass.conf (on windows)/.pgpass
    (on non-windows)
  * Fix a segfault occurs while detecting transaction section requirement,
    when autocommit has been disabled.
  * Format execution time in a more readable manner
  * Improve sorting in Data editor
  * Allow to format the selecte SQL using external tools in Query Editor
  * Allow to set auto-commit mode to on/off in the query editor
  * Do not try unlock the mutex, which was not owned by the thread, while
    creating the popup menu
  * Set the focus on browser tree windows on startup
  * Make the arrow key navigation consistent across all platform on the
    object browser tree
  * Show indexes for the materialized views in Query pane
  * Add support for searching materialized views in the</changelog>
  <changelog author="crrodriguez@opensuse.org" date="1456660800">- remove obsolete suse_version checks
- fix debuginfo generation.</changelog>
  <changelog author="crrodriguez@opensuse.org" date="1456660801">- Update to version 1.22.1
  * Don't barf when connecting to Greenplum or Greenplum HAWQ
  * Fix selection of conversion functions in the CREATE CONVERSION dialogue.
  * Properly quote type names in the Type dialogue, andensure range
  information is displayed for existing types
  * Fix selection of cast functions in the Cast dialogue</changelog>
  <changelog author="martin.liska@suse.com" date="1467374400">- Add -fno-delete-null-pointer-checks to CXXFLAGS to workaround
  boo#986857.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to version 1.22.2
  * Include the Negator when reverse engineering SQL for operators
  * Fix the psql plugin command on OSX to work more reliably
  * Prevent a crash in some situtions where the database connection
  is lost and needs to be reset.
  * Fix display of elapsed query time for queries running longer than
  1 hour
- This is the final release of pgadmin3</changelog>
  <changelog author="bruno@ioda-net.ch" date="1485691200">- Packaging :
  + spec-clean minimal
  + remove obsolete version sle and openSUSE
  + globalize \r removal in css files
  + use wxWidgets-3_0-nostl-devel to remove dependency of gst 0.10
    so use internal dependency generator on openSUSE &gt; 1315
  + Add WX_VER variable to build correctly
  + Added patch wxWidget-limit-libs-used.patch to explicitely add
    the needed libs.
  + Try to handle differents WX versions between openSUSE and SLE</changelog>
  <changelog author="bruno@ioda-net.ch" date="1492516800">- Add 0001-Set-row-heights-based-on-pixels-rather-than-points.patch
  Fix control grid row on hidpi screen.</changelog>
</package>
<package pkgid="53c3397aefdcd2056ba3cf05f780216908ef9323a094fa60fd454ce6532195c2" name="pgadmin3-lang" arch="noarch">
  <version epoch="0" ver="1.22.2" rel="39.4"/>
  <changelog author="saschpe@gmx.de" date="1296734400">- added dependency on wxWidgets for openSUSE-11.4 and greater</changelog>
  <changelog author="mrueckert@suse.de" date="1298980800">- use wx_requires on 11.4 and newer</changelog>
  <changelog author="klaussfreire@gmail.com" date="1301313600">- update to upstream git 2011-03-28</changelog>
  <changelog author="saschpe@suse.de" date="1302523200">- set license to 'PostgreSQL', fixes bnc#675943</changelog>
  <changelog author="klaussfreire@gmail.com" date="1316174400">- update to upstream 1.14.0
  * see http://www.pgadmin.org/development/changelog.php</changelog>
  <changelog author="coolo@suse.com" date="1322827200">- add automake as buildrequire to avoid implicit dependency</changelog>
  <changelog author="pascal.bleser@opensuse.org" date="1340539200">- update to 1.14.3:
  http://www.pgadmin.org/development/changelog.php</changelog>
  <changelog author="bruno@ioda-net.ch" date="1359374400">- fix bnc#800831
- update to 1.16.1
  http://www.pgadmin.org/development/changelog.php
    Date       Dev Ver     Change details
  - --------- --- ------  --------------
    2012-12-03 DP  1.16.1  Prevent a crash that could happen if further changes
  were made on a dialogue after using the Apply button.
  [Akshay Joshi]
    2012-11-29 GL  1.16.1  Save new comments on already existing columns when
  editing a table. Per a report from Jeff Janes.
    2012-11-29 GL  1.16.1  Fix the query editor behaviour when executing COPY TO
  stdout and COPY FROM stdin [Heikki Linnakangas]
    2012-11-28 AV  1.16.1  Date picker controls returns a full timestamp by
  default, which can cause inadvertent date changes
  on jobs and role validty dates. Ignore the time part.
    2012-11-26 MH  1.16.1  Fix query for database descriptions
    2012-11-15 DP  1.16.1  Avoid querying the catalogs for toast table settings
  for every table in the database. This gives a huge
  performance gain with large schemas.
    2012-11-08 DP  1.16.1  Prevent a crash when refreshing a node which has a
  child with an open dialogue [Dhiraj Chawla]
    2012-11-08 DP  1.16.1  Fix dropping/renaming of indexes [Akshay Joshi]
    2012-11-08 DP  1.16.1  Avoid updating the GQB model on every key press in
  the query tool [Dhiraj Chawla]
    2012-11-02 DP  1.16.1  Fix a crash that can occur when renaming objects.
  [Ashesh Vashi/Sachin Srivastava]
    2012-11-01 DP  1.16.1  Fix dropping of constraints [Akshay Joshi]
    2012-10-31 DP  1.16.1  Fix the "blocked by" column in the server status
  dialogue on 9.2 servers [Sachin Srivastava]
    2012-10-11 DP  1.16.1  Prevent a crash if the query tool is closed whilst a
  file is loading [Akshay Joshi]
    2012-10-09 AV  1.16.1  Fix setting of comments on PPAS procedures.
    2012-10-08 DP  1.16.1  Don't autosize the search results columns if no
  results are found [Akshay Joshi]
    2012-10-08 AV  1.16.1  Prevent a crash if opening a second config file in
  the editor.
    2012-10-08 DP  1.16.1  Prevent the SSL options combo box displaying
  duplicate options if the server dialogue is
  reopened [Akshay Joshi]
    2012-09-14 GL  1.16.1  Fix trigger query when connected to PostgreSQL 8.2 or
  lower, per a report from Jon Roberts.
    2012-09-12 GL  1.16.1  Fix message when executing an empty query, per Marc
  Mamin.
    2012-05-08 GL  1.16.0  Add privilege support on aggregates.
    2012-05-05 GL  1.16.0  Add inline function support on languages.
    2012-04-29 GL  1.16.0  Add support for range types.
    2012-04-28 GL  1.16.0  Add support for setting db/user config on dlgRole.
    2012-04-08 GL  1.16.0  Move references table textbox to the third tab in
  dlgForeignKey. Per request from Colin Beckingham.
    2012-04-05 GL  1.16.0  Support for the new two columns in 9.2 pg_stat_database
    2012-03-12 GL  1.16.0  Support for renaming constraints (9.2).
    2012-03-02 GL  1.16.0  Fix wxWidgets 2.9 compatibility with pgAdmin on Linux
  [Akshay Joshi].
    2012-02-23 GL  1.16.0  New import tool.
    2012-02-15 GL  1.16.0  Support for the LEAKPROOF option in functions.
    2012-02-13 GL  1.16.0  Support ANALYZE, CATEGORY, and PREFERED items for
  CREATE TYPE statement.
    2012-02-11 GL  1.16.0  Support CREATE TABLE LIKE.
    2012-02-09 GL  1.16.0  Support for the new TIMING option in EXPLAIN ANALYZE.
    2012-01-26 GL  1.16.0  Support for the new three columns in 9.2 pg_stat_database
    2012-01-22 GL  1.16.0  Use date_trunc to skip the microseconds part of all
  timestamp fields in frmStatus.
    2012-01-22 GL  1.16.0  Support new/changed pg_stat_activity fields.
    2012-01-08 GL  1.16.0  Allow renaming a domain.
    2012-01-07 GL  1.16.0  Add subitems to the schemas and catalogs in GQB.
  Request from Colin Beckingham.
    2012-01-05 GL  1.16.0  Support section options for pg_dump/pg_restore.
    2012-01-03 GL  1.16.0  Add security_barrier option handling for views.
    2011-12-19 DP  1.16.0  Add an "New Folder" button to the "Add Favourite" dialog
  in the query tool [Dhiraj Chawla]
    2011-12-12 GL  1.16.0  Support for the new sslcompression connection option.
    2011-12-11 GL  1.16.0  Add renaming of FDW and Server objects.
    2011-12-10 GL  1.16.0  Support for TRUNCATE permission
    2011-09-10 GL  1.16.0  Reverse engineering in the database designer.
  Patch from Luis Ochoa with some fixes by me.
    2011-09-04 GL  1.16.0  Highlight the other brace even if the current one is
  before the caret (request from Andreas).
    2011-08-24 DP  1.16.0  Add options to refresh objects automatically when
  clicked [Vinicius Santos]
    2011-08-15 GL  1.16.0  Redesign frmOptions.
    2011-08-11 GL  1.16.0  Prevents dropping connection, dropping or refreshing
  object when a properties dialog is open.
    2011-08-11 GL  1.16.0  Support for multimodels diagram in the database
  designer. Patch from Luis Ochoa with some fixes by me.
    2011-08-07 GL  1.16.0  Implement enable/disable save button, on text change.
  Patch from Vinicius Santos.
    2011-07-25 GL  1.16.0  Change doc build system.
    2011-07-25 GL  1.16.0  Support for security labels on global/shared objects
  (9.2 feature).
    2011-07-25 GL  1.16.0  Support for security labels on local objects (9.1
  feature).
    2011-07-25 GL  1.16.0  Support for non valid domains, and check constraints
  (9.2 feature).
    2011-07-25 GL  1.16.0  Add load/save support for the Database Designer. Patch
  from Luis Ochoa.
    2011-07-09 GL  1.16.0  Allow change of schema in the UI. Patch from Thom
  Brown.
    2011-07-05 GL  1.16.0  Add "Search Objects" dialog. Patch from Jasmin Dizdarevic.
    2011-07-03 GL  1.16.0  New maintenance action: CLUSTER. Patch from Thom Brown.
    2011-07-02 GL  1.16.0  Enable "Has OIDs" on 8.4+ even when the table is
  already created. Patch from Thom Brown.
    2011-06-27 GL  1.16.0  Add Database Designer. Patch from Luis Ochoa.
    2011-06-23 DP  1.16.0  Allow change of the fill factor. Patch from Thom Brown.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1382184000">- spec remove cleaning png2c (fixed in 1.18)
- update to 1.18.1
  http://www.pgadmin.org/development/changelog.php
  Date       Dev Ver     Change details
  - --------- --- ------  --------------
  2013-09-29 GL  1.18.1  Allow the dump of pg&lt;something&gt; schemas.
  2013-09-26 DP  1.18.1  Prevent a crash on Windows when dropping a column or a
  constraint on a table [Dhiraj Chawla]
  2013-09-26 DP  1.18.1  Ensure DDLScript will work with Slony 2.2+ which has a
  new SQL level API [Neel Patel]
  2013-09-26 DP  1.18.1  Fix ordering of object types in the display options and
  add Event Triggers which were missing [Dhiraj Chawla].
  2013-09-21 AV  1.18.1  Ensure the debugger can cope with functions that have an
  OUT parameter as the first.
  2013-09-19 DP  1.18.1  Fix the quoting of user mapping objects [Dinesh Kumar]
  2013-09-19 DP  1.18.1  Ensure that materialised views are available as targets
  for synonyms [Neel Patel]
  2013-09-19 DP  1.18.1  Fix the query used to find tables in a Slony
  replication set [Neel Patel]
  2013-09-11 DP  1.18.1  Prevent a crash if a user starts an external process
  such as a backup, and then immediately hits cancel
  [Neel Patel].
  2013-09-06 DP  1.18.1  Fix a memory leak in the Event Trigger code [Dinesh
  Kumar].
  2013-08-20 AV  1.18.0  Fix a layout bug in the graphical explain renderer that
  could render nodes on top of each other.
  2013-08-06 DP  1.18.0  Fix Slony's DDL Script support [Akshay Joshi].
  2013-07-26 DP  1.18.0  Add support for Event Triggers in 9.3+ [Dinesh Kumar].
  2013-07-22 DP  1.18.0  Avoid using a Help cache file that needs to be world
  writeable, and ensure sed is happy when post-processing
  helpfiles.
  2013-07-22 DP  1.18.0  Fix the help path on the import dialogue and improve the
  error handling [Akshay Joshi].
  2013-07-22 DP  1.18.0  Fix path the the Search Objects help doc [Dhiraj Chawla].
  2013-07-18 GL  1.18.0  Fix UTF-8 display for guru hints [Marek Cernocky].
  2013-07-08 DP  1.18.0  Prevent a crash when creating a stored procedure in
  PPAS [Dinesh Kumar].
  2013-06-19 GL  1.18.0  Disable the Favourites menu items if there is no
  favourites file path (per a comment from Michael Shapiro).
  2013-06-18 GL  1.18.0  Make No the default button on the Truncate confirmation
  dialog (per request from Humberto Cereser Ibanez).
  2013-06-18 DP  1.18.0  Support Materialized Views [Neel Patel].
  2013-06-07 DP  1.18.0  Avoid a possible crash on Linux when using the
  "Script" options of the Query Tool [aditsu].
  2013-05-26 DP  1.18.0  Fix comments on constraints [Thom Brown].
  2013-05-26 DP  1.18.0  Fix schema prefixes in cast definitions in the browser.
  2013-05-26 DP  1.18.0  Treat sequences as first class objects in the Grant
  Wizard. Support USAGE and remove obsolete RULE
  permissions [Dhiraj Chawla].
  2013-05-26 DP  1.18.0  Set the default backup type to "Custom".
  2013-05-21 DP  1.18.0  Improve the copy handling on the Edit Grid so that
  it works more consistently and predictably.
  2013-05-20 DP  1.18.0  Fix comments on columns.
  2013-05-20 DP  1.18.0  Remove the "Apply" buttons from the function, view
  package and external table dialogues. Their use is
  discouraged, and the code is fragile, complex and
  very buggy.
  2013-05-20 DP  1.18.0  Fix a crash that could occur if the browser fails to
  detect that an object has been changed by another
  session.
  2013-05-17 DP  1.18.0  Change the default SQL box font to a slightly smaller
  size on GTK based platforms.
  2013-05-17 DP  1.18.0  Don't prompt the user for a password if they're using
  a client certificate.
  2013-05-17 DP  1.18.0  Ensure global backups use the mintenance database to
  avoid access issue with postgres or template1.
  2013-05-17 DP  1.18.0  Fix SSL certificate authentication.
  2013-05-08 DP  1.18.0  Fix renaming and schema changes for stored procedures
  in PPAS [Dinesh Kumar].
  2013-05-02 DP  1.18.0  Add SSH tunnelling support to allow connections to be
  made to hosts via an SSH server [Akshay Joshi].
  2013-05-02 DP  1.18.0  Display the index validity in the properties list for
  indexes and index-based constraints [Gabrielle Roth].
  2013-04-29 DP  1.18.0  Add an option to include column headers when copying
  from the query tool results [Jasmin Dizdarevic].
  2013-04-29 DP  1.18.0  Allow the decimal mark displayed by the query tool to be
  configured as the thousands separator can [Jasmin
  Dizdarevic].
  2013-04-25 DP  1.18.0  Ensure the Query Tool's maximum column length setting
  is honoured.
  2013-04-22 DP  1.18.0  Handle default privileges to PUBLIC correctly. [Dhiraj
  Chawla].
  2013-03-24 GL  1.18.0  Add tab option in the Import dialog. Per a request from
  Jeff Janes.
  2013-03-17 GL  1.18.0  Add smallserial handling. Per a request from Matthew
  Syphus.
  2013-03-01 DP  1.18.0  Fix the editing of pg_hba.conf files [Dhiraj Chawla].
  2013-02-25 DP  1.18.0  Fix the display of extension owner names.
  2013-02-23 GL  1.18.0  Add a title to the backup and restore windows. Per
  request from Bastiaan Olij.
  2013-02-22 DP  1.18.0  Fix a bug that could cause a NOTICE to be displayed
  when rendering FTS Configurations in the tree.
  2013-02-07 DP  1.18.0  Don't try to display dependents or dependencies for
  pgAgent jobs, schedules or steps.
  2013-02-06 DP  1.18.0  Fix the handling of expiry times when modifying roles.
  2013-02-04 DP  1.18.0  Prevent foreign keys being recreated unnecessarily when
  modifying tables [Michael Banck]
  2013-01-24 DP  1.18.0  Prevent Cmd+S adding characters to the Query Tool when
  the Save button is disabled.
  2013-01-18 DP  1.18.0  Fix handling of Greenplum partitions [Lubomir Petrov]
  2013-01-06 GL  1.18.0  Add -V/--version CLI option.
  2013-01-06 GL  1.18.0  Add actions menu to the serverstatus tool.
  2013-01-06 GL  1.18.0  Fix the database SQL when reseting a configuration
  parameter. Per a report from Bartosz Dmytrak.
  2013-01-04 GL  1.18.0  Refresh the toolbar buttons when a list has been
  updated. Per a report from Evan Martin.
  2013-01-04 GL  1.18.0  Fix the "NO INHERIT" query. Report from Thomas Joseph.
  2012-12-24 GL  1.18.0  Display default privs. Report from Nathan Alden.
  2012-12-24 GL  1.18.0  Sort references by schema name and relation name in
  dlgForeignKey. Report from Michal Kozusznik.
  2012-12-24 GL  1.18.0  Fix the change of the superuser attribute. Report from
  Michal Kozusznik.
  2012-12-18 DP  1.18.0  Prevent a crash when using Cmd-A on a file loaded into
  the Query Tool when opened with Cmd-E on Mac.
  2012-12-07 DP  1.18.0  Fix the queries used to get object comments to allow
  for duplicate OIDs that may be present following use
  of pg_upgrade.</changelog>
  <changelog author="max@suse.com" date="1386849600">- Remove broken and unneeded dependency on libecpg (bnc#854754).</changelog>
  <changelog author="termim@gmail.com" date="1422446400">- update to 1.20.0
  * Resolving the inconsistency of preservation of modified
    information of the columns, while adding/editing a table from
    the table dialog
  * Add missing nodes to graphical explain plan
  * Fix the Resource Groups dialog - separated the statements,
    which can not be ran in single transaction
  * Support for Slony-I 2.2+ with PostgreSQL 9.3+
  * Support smallserial columns in Edit Data Window
  * Restore the user specified size on the grid (which contains the
    result) in Query windows to fix an issue related to the column
    size is too narrow on subsequent Explain execution
  * Empty the Undo/Redo history everytime new file is opened
  * Added accelerator F8 for 'Execute to file' in the Query window
  * Beautify the query shown in the SQL pane for the functions
    having multiple arguments by adding new lines with small
    modification
  * Check for the columnlist for the UPDATE OF syntax on trigger
    also works with PPAS 9.5+
  * Proper saving of columns width in the server status window
  * CHECK OPTION is applicable to the views only, and not the
    materialized views
  * Prevent a crash during the update of the macro or favourite
    list
  * Allow quick injectection of favourites by name
  * Fix handling of saving macros after pasting a query in the box
  * Fix handling of char()[] columns in the Edit Grid
  * Support the new check_option parameter of views
  * Handle the 9.4 MOVE clause of ALTER TABLESPACE
  * Add a new action menu to refresh a materialized view
  * Support the new 9.4 columns in pg_stat_activity
  * Save search options for next time
  * Ensure Favourite queries are only saved when the OK button is
    pressed
  * Fix an issue refreshing functions in PPAS packages
  * Improve handling of lost connections
  * Allow searching for database objects by comment and definition
    content
  * Add support for Resource Groups in PPAS 9.4
  * Add Save and Exit shortcut keys to the edit grid
  * Enable backward search in SQL Box using Shift + F3
  * Allow more flexible selection/deselection of rows and columns
    in Edit Grid
  * Allow more options with the plain backup.
  * Use a much smarter auto-sizing algorithm for the columns in the
    Query Tool output grid.
  * Remember the last panel used on the Options dialogue, and
    display the default panel if a group node is selected on the
    tree
  * Allow parallel dump with -j starting with 9.3
- update to 1.18.2
  * Fix SQL for GRANT on a sequence. Report from liuyuanyuan.
  * Fix escape handling in pgpass files
  * GQB forgot the materialized views.
  * Don't set log_min_messages from the debugger
  * Fix a crash on OSX when run explain through shortcut in query
    editor, when mouse is over a existing shape, and popup, showing
    the step information, is on
  * Using the GetOid() function instead of GetLong() for Oid
    columns
  * Fix SQL comments for inherited columns.
  * Flush the changes in the settings as soon as new server is
    added
  * Don't include obsolete config settings from &lt;= 8.3 in the
    config editor unless running on an appropriate server.
  * Ensure the Type dialogue detects name changes.
  * Ensure report titles don't overflow the page width
  * Ensure reports overflow the page width properly
  * Add missing "port" option for SSH tunnels.
  * Set 32bit PostgreSQL, EnterpriseDB PATH (in case - 64bit
    respective applications not found, and 32bit(s) are available)
    for 64bit pgAdmin III.
  * Improved the debugger to work better with PPAS &lt;= 9.2
  * Fix the handling of the "Valid Until" date/time on the role
    dialogue on Mac.</changelog>
  <changelog author="mpluskal@suse.com" date="1439380800">- Add explicit dependencies on autoconf and libtool</changelog>
  <changelog author="jweberhofer@weberhofer.at" date="1444996800">- Do not recommend but only suggest to install postgresql-server.</changelog>
  <changelog author="termim@gmail.com" date="1453809600">- update to 1.22.0
  * Resolved an issue related to check options selection in the view
    properties dialog with the check option.
  * Merged the libssh2 to the latest version.
  * Properly detect serial columns as such when identifiers have been
    truncated.
  * Fixes an issue related to the column inheritance information properly,
    when one (or, more) common columns are inherited from multiple tables.
  * Ensure the correct syntax used for moving the objects from one
    tablespace to another.
  * Ensure the correct line endings are used when copying from the SQL Pane
  * Toolbar icons, and menu items for Commit and Rollback actions.
  * Display the connection details for the current browser object in the
    status bar
  * Fixed an issue related to different menus enabling in the Query Tool on
    Ubunutu unity.
  * Reset the position (x, y) for dialog(s), and frame(s) to 0 (if found
    negative), while saving its position and size.
  * Fixes an issue identifying the return type to TABLE in some cases,
    using pg_get_function_result(..) for the same instead of format_type(..)
  * Honour PGPASSFILE environment variable for saving, retrieving the
    password instead of always works with pgpass.conf (on windows)/.pgpass
    (on non-windows)
  * Fix a segfault occurs while detecting transaction section requirement,
    when autocommit has been disabled.
  * Format execution time in a more readable manner
  * Improve sorting in Data editor
  * Allow to format the selecte SQL using external tools in Query Editor
  * Allow to set auto-commit mode to on/off in the query editor
  * Do not try unlock the mutex, which was not owned by the thread, while
    creating the popup menu
  * Set the focus on browser tree windows on startup
  * Make the arrow key navigation consistent across all platform on the
    object browser tree
  * Show indexes for the materialized views in Query pane
  * Add support for searching materialized views in the</changelog>
  <changelog author="crrodriguez@opensuse.org" date="1456660800">- remove obsolete suse_version checks
- fix debuginfo generation.</changelog>
  <changelog author="crrodriguez@opensuse.org" date="1456660801">- Update to version 1.22.1
  * Don't barf when connecting to Greenplum or Greenplum HAWQ
  * Fix selection of conversion functions in the CREATE CONVERSION dialogue.
  * Properly quote type names in the Type dialogue, andensure range
  information is displayed for existing types
  * Fix selection of cast functions in the Cast dialogue</changelog>
  <changelog author="martin.liska@suse.com" date="1467374400">- Add -fno-delete-null-pointer-checks to CXXFLAGS to workaround
  boo#986857.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to version 1.22.2
  * Include the Negator when reverse engineering SQL for operators
  * Fix the psql plugin command on OSX to work more reliably
  * Prevent a crash in some situtions where the database connection
  is lost and needs to be reset.
  * Fix display of elapsed query time for queries running longer than
  1 hour
- This is the final release of pgadmin3</changelog>
  <changelog author="bruno@ioda-net.ch" date="1485691200">- Packaging :
  + spec-clean minimal
  + remove obsolete version sle and openSUSE
  + globalize \r removal in css files
  + use wxWidgets-3_0-nostl-devel to remove dependency of gst 0.10
    so use internal dependency generator on openSUSE &gt; 1315
  + Add WX_VER variable to build correctly
  + Added patch wxWidget-limit-libs-used.patch to explicitely add
    the needed libs.
  + Try to handle differents WX versions between openSUSE and SLE</changelog>
  <changelog author="bruno@ioda-net.ch" date="1492516800">- Add 0001-Set-row-heights-based-on-pixels-rather-than-points.patch
  Fix control grid row on hidpi screen.</changelog>
</package>
<package pkgid="96f5d64a95a30f5739a21a7be55662328d3c841ca3b77a20f68e7bfb98c8466b" name="pgbackrest" arch="noarch">
  <version epoch="0" ver="1.17" rel="1.1"/>
  <changelog author="mrueckert@suse.de" date="1462363200">- update to 1.00</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- added pgbackrest-release-1.00_datadir.patch:
  perl libraries installed in the normal search path we dont need
  this anymore.</changelog>
  <changelog author="mrueckert@suse.de" date="1478779200">- update to 1.10
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.10
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.09
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.08
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.07
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.06
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.05
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.04
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.03
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.02
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.01</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 1.13
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.13
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.12
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.11</changelog>
  <changelog author="bruno@ioda-net.ch" date="1490097600">- update to 1.17
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.17
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.16
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.15
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.14</changelog>
</package>
<package pkgid="c3bdb51a5bd5c6c29458a57421d3ab34c6f10bc054393210788942c62d7865c7" name="pgbackrest" arch="src">
  <version epoch="0" ver="1.17" rel="1.1"/>
  <changelog author="mrueckert@suse.de" date="1462363200">- update to 1.00</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- added pgbackrest-release-1.00_datadir.patch:
  perl libraries installed in the normal search path we dont need
  this anymore.</changelog>
  <changelog author="mrueckert@suse.de" date="1478779200">- update to 1.10
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.10
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.09
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.08
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.07
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.06
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.05
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.04
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.03
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.02
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.01</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 1.13
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.13
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.12
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.11</changelog>
  <changelog author="bruno@ioda-net.ch" date="1490097600">- update to 1.17
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.17
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.16
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.15
  https://github.com/pgbackrest/pgbackrest/releases/tag/release%2F1.14</changelog>
</package>
<package pkgid="28571977c5cc003b6a0fc80cb1afa65a298d8959169d7e536b12b9f4386c96e2" name="pgbadger" arch="noarch">
  <version epoch="0" ver="8.1" rel="2.1"/>
  <changelog author="lars@linux-schulserver.de" date="1357473600">- initial version 2.2-1</changelog>
  <changelog author="darin@darins.net" date="1360756800">- update to 2.3
  * Clarify misleading statement about log_duration: log_duration may be
    turned on depending on desired information. Only log_statement must
    not be on. Thanks to Matt Romaine for the patch.
  * Fix --dbname and --dbuser not working with csvlog format. Thanks to
    Luke Cyca for the report.
  * Fix issue in SQL formatting that prevent left back indentation when
    major keywords were found. Thanks to Kevin Brannen for the report.
  * Display 3 decimals in time report so that ms can be seen. Thanks to
    Adam Schroder for the request.
  * Force the parser to not insert a new line after the SET keyword when
    the query begin with it. This is to preserve the single line with
    queries like SET client_encoding TO "utf8";
  * Add better SQL formatting of update queries by adding a new line
    after the SET keyword. Thanks to pilat66 for the report.
  * Update copyright and documentation.
  * See ChangeLog
- added missing perl dependency for cvs logs</changelog>
  <changelog author="lars@linux-schulserver.de" date="1364040000">- update to 3.1:
  !! UPGRADE: if you are running pgbadger by cron take care if you
  !! were using one of the following option: --enable-log_min_duration
  !! and --enable-log_duration, they have been removed and pgbadger
  !! will refuse to start
  + This new major release adds parallel log processing by using as
    many cores as wanted to parse log files, the performances gain is
    directly related to the number of cores specified.
    There's also new reports about autovacuum/autoanalyze informations
    and many bugs have been fixed.
  + Please read the full Changelog at:
    /usr/share/doc/packages/pgbadger/ChangeLog
- do not use perl_gen_filelist macro on old distributions:
  breaks build
- removed duplicated perl(Text::CSV_XS) build requires line</changelog>
  <changelog author="lars@linux-schulserver.de" date="1367841600">- update to 3.3:
  * adds four more useful reports about queries that generate locks
    and temporary files
  * new report about restartpoint on slaves and several
  * adds escaping of HTML code inside queries
  * adds Min/Max reports with Average duration in all queries reports
  * many bug fixes</changelog>
  <changelog author="lars@linux-schulserver.de" date="1394625600">- update to 5.0:
  + This new major release adds some new features like incremental
    mode and SQL queries times histogram. There is also a hourly
    graphic representation of the count and average duration of top
    normalized queries.
  + there are many more changes, please refer to
    /usr/share/doc/packages/pgbadger/ChangeLog
    for details</changelog>
  <changelog author="darin@darins.net" date="1413288000">- update to 6.2
  + This is a maintenance release to fix a regression in SQL traffic graphs and
    fix some other minor issues.
  + The release also add a new option -D or --dns-resolv to map client ip addresses
    to FQDN without having log_hostname enabled on the postgresql's configuration
  + Do not display queries in Slowest individual, Time consuming and
    Normalized slowest queries reports when there is no duration in
    log file. Display NO DATASET instead.
  + Fix min/max queries in SQL traffic that was based on duration instead
    of query count.
  + Fix wrong unit to Synced files in Checkpoints files report. Thanks
    to Levente Birta for the report.
  + Enable allow_loose_quotes in Text::CSV_XS call to fix CSV parsing
    error when fields have quote inside an unquoted field. Thanks to
    Josh Berkus for the report.
  +- Add -D | --dns-resolv command line option to replace ip addresses
    by their DNS name. Be warned that this can slow down pgBagder a lot.
    Thanks to Jiri Hlinka for the feature request.</changelog>
  <changelog author="lars@linux-schulserver.de" date="1442145600">- update to 7.1:
  + This new release fixes some issues and adds a new report:
  ++ Distribution of sessions per application
  + It also adds Json operators to SQL Beautifier.
  + this release also adds some more useful reports and features,
    please check the changes file in
    /usr/share/doc/packages/pgbadger/ChangeLog for details
- remove perl vendorarch directory if empty
- also package pgbadger_tools in doc directory
- add rpmlintrc to get rid of the license warning</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 8.1
  - Fix one case where pid file remain after dying.
  - Add requirement of log_error_verbosity = default to
    documentation.
  - Report message "LOG: using stale statistics instead of current
    ones because stats collector is not responding" in events view.
  - Remove obsolete days when we are in binary mode with --noreport
  - Fix wrong report of statements responsible of temporary files.
    Thanks to Luan Nicolini Marcondes for the report. This patch
    also exclude line with log level LOCATION to be parsed.
  - Fix limit on number of sample at report generation and remove
    pending LAST_PARSED.tmp file.
  - Update load_stat() function and global variables to support
    pgbouncer statistics. Update version to 2.0.
  - Handle more kind or query types. Thanks to julien Rouhaud for
    the patch.
  - Fix pgbouncer log parser to handle message: FATAL: the database
    system is shutting down
  - Fix whitespace placed in between the E and the quote character.
    Thanks to clijunky for the report.
  - Fix a major issue introduced with support to pgbouncer that
    prevent parsing of compressed PostgreSQL log files. Thanks to
    Levente Birta for the report.
- remove the unused rpmlintrc</changelog>
</package>
<package pkgid="a6df96df9455f96136b673b5a20df920e8d9a906decee1f28c2b76925f638327" name="pgbadger" arch="src">
  <version epoch="0" ver="8.1" rel="2.1"/>
  <changelog author="lars@linux-schulserver.de" date="1357473600">- initial version 2.2-1</changelog>
  <changelog author="darin@darins.net" date="1360756800">- update to 2.3
  * Clarify misleading statement about log_duration: log_duration may be
    turned on depending on desired information. Only log_statement must
    not be on. Thanks to Matt Romaine for the patch.
  * Fix --dbname and --dbuser not working with csvlog format. Thanks to
    Luke Cyca for the report.
  * Fix issue in SQL formatting that prevent left back indentation when
    major keywords were found. Thanks to Kevin Brannen for the report.
  * Display 3 decimals in time report so that ms can be seen. Thanks to
    Adam Schroder for the request.
  * Force the parser to not insert a new line after the SET keyword when
    the query begin with it. This is to preserve the single line with
    queries like SET client_encoding TO "utf8";
  * Add better SQL formatting of update queries by adding a new line
    after the SET keyword. Thanks to pilat66 for the report.
  * Update copyright and documentation.
  * See ChangeLog
- added missing perl dependency for cvs logs</changelog>
  <changelog author="lars@linux-schulserver.de" date="1364040000">- update to 3.1:
  !! UPGRADE: if you are running pgbadger by cron take care if you
  !! were using one of the following option: --enable-log_min_duration
  !! and --enable-log_duration, they have been removed and pgbadger
  !! will refuse to start
  + This new major release adds parallel log processing by using as
    many cores as wanted to parse log files, the performances gain is
    directly related to the number of cores specified.
    There's also new reports about autovacuum/autoanalyze informations
    and many bugs have been fixed.
  + Please read the full Changelog at:
    /usr/share/doc/packages/pgbadger/ChangeLog
- do not use perl_gen_filelist macro on old distributions:
  breaks build
- removed duplicated perl(Text::CSV_XS) build requires line</changelog>
  <changelog author="lars@linux-schulserver.de" date="1367841600">- update to 3.3:
  * adds four more useful reports about queries that generate locks
    and temporary files
  * new report about restartpoint on slaves and several
  * adds escaping of HTML code inside queries
  * adds Min/Max reports with Average duration in all queries reports
  * many bug fixes</changelog>
  <changelog author="lars@linux-schulserver.de" date="1394625600">- update to 5.0:
  + This new major release adds some new features like incremental
    mode and SQL queries times histogram. There is also a hourly
    graphic representation of the count and average duration of top
    normalized queries.
  + there are many more changes, please refer to
    /usr/share/doc/packages/pgbadger/ChangeLog
    for details</changelog>
  <changelog author="darin@darins.net" date="1413288000">- update to 6.2
  + This is a maintenance release to fix a regression in SQL traffic graphs and
    fix some other minor issues.
  + The release also add a new option -D or --dns-resolv to map client ip addresses
    to FQDN without having log_hostname enabled on the postgresql's configuration
  + Do not display queries in Slowest individual, Time consuming and
    Normalized slowest queries reports when there is no duration in
    log file. Display NO DATASET instead.
  + Fix min/max queries in SQL traffic that was based on duration instead
    of query count.
  + Fix wrong unit to Synced files in Checkpoints files report. Thanks
    to Levente Birta for the report.
  + Enable allow_loose_quotes in Text::CSV_XS call to fix CSV parsing
    error when fields have quote inside an unquoted field. Thanks to
    Josh Berkus for the report.
  +- Add -D | --dns-resolv command line option to replace ip addresses
    by their DNS name. Be warned that this can slow down pgBagder a lot.
    Thanks to Jiri Hlinka for the feature request.</changelog>
  <changelog author="lars@linux-schulserver.de" date="1442145600">- update to 7.1:
  + This new release fixes some issues and adds a new report:
  ++ Distribution of sessions per application
  + It also adds Json operators to SQL Beautifier.
  + this release also adds some more useful reports and features,
    please check the changes file in
    /usr/share/doc/packages/pgbadger/ChangeLog for details
- remove perl vendorarch directory if empty
- also package pgbadger_tools in doc directory
- add rpmlintrc to get rid of the license warning</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 8.1
  - Fix one case where pid file remain after dying.
  - Add requirement of log_error_verbosity = default to
    documentation.
  - Report message "LOG: using stale statistics instead of current
    ones because stats collector is not responding" in events view.
  - Remove obsolete days when we are in binary mode with --noreport
  - Fix wrong report of statements responsible of temporary files.
    Thanks to Luan Nicolini Marcondes for the report. This patch
    also exclude line with log level LOCATION to be parsed.
  - Fix limit on number of sample at report generation and remove
    pending LAST_PARSED.tmp file.
  - Update load_stat() function and global variables to support
    pgbouncer statistics. Update version to 2.0.
  - Handle more kind or query types. Thanks to julien Rouhaud for
    the patch.
  - Fix pgbouncer log parser to handle message: FATAL: the database
    system is shutting down
  - Fix whitespace placed in between the E and the quote character.
    Thanks to clijunky for the report.
  - Fix a major issue introduced with support to pgbouncer that
    prevent parsing of compressed PostgreSQL log files. Thanks to
    Levente Birta for the report.
- remove the unused rpmlintrc</changelog>
</package>
<package pkgid="936424086a4540797042513140330aa9231eeec32609c3aa2c5cf61878e0d391" name="pgbouncer" arch="src">
  <version epoch="0" ver="1.7.2" rel="3.2"/>
  <changelog author="mrueckert@suse.de" date="1300536000">- initial package (v1.4)</changelog>
  <changelog author="mrueckert@suse.de" date="1300536001">- install documentation
- build with verbose to see the compiler cmdlines</changelog>
  <changelog author="mrueckert@suse.de" date="1300536002">- moved binaries to _sbindir
- added init script
- added user and group
- added pgbouncer-1.4_default_config.patch
  change path for pid file and log file
- create log file in %install for proper permissions
- added logrotate file</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- fix build on older sle versions</changelog>
  <changelog author="mrueckert@suse.de" date="1302782401">- revert it, libevent is too old even on sle10</changelog>
  <changelog author="mrueckert@suse.de" date="1354017600">- update to 1.5.3: (CVE-2012-4575)
  see /usr/share/doc/packages/pgbouncer/NEWS
- drop pgbouncer-1.4_default_config.patch:
  applied upstream</changelog>
  <changelog author="darin@darins.net" date="1362744000">- Update to 1.5.4
  * DNS: Fix memory leak in getaddrinfo_a() backend.
  * DNS: Fix memory leak in udns backend.
  * DNS: Fix stats calculation.
  * DNS: Improve error message handling for getaddrinfo_a().
  * Fix win32 compile.
  * Fix compiler dependency support check in configure.
  * Few documentation fixes.</changelog>
  <changelog author="adam@mizerski.pl" date="1371556800">- fixed creation of system user</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 1.7.2
  all changes inbetween:
  https://pgbouncer.github.io/changelog.html#pgbouncer-17x
  https://pgbouncer.github.io/changelog.html#pgbouncer-16x
  https://pgbouncer.github.io/changelog.html#pgbouncer-15x</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- they use methods now that require openssl 1.0</changelog>
  <changelog author="mrueckert@suse.de" date="1467892801">- pull 3 patches from upstream:
  0001-tls-do-not-ask-TLS-on-unix-socket.patch
  0002-tls-reject-client-TLS-request-on-unix-socket.patch
  0003-hba-Skip-unparseable-lines-keep-parsing-to-the-end.patch
- fix service file reload action</changelog>
</package>
<package pkgid="328c6fbb1efe3ab1fa0e590d2951e38135db3c0db49c923a5f8ab4f17e7ad180" name="pgbouncer" arch="x86_64">
  <version epoch="0" ver="1.7.2" rel="3.2"/>
  <changelog author="mrueckert@suse.de" date="1300536000">- initial package (v1.4)</changelog>
  <changelog author="mrueckert@suse.de" date="1300536001">- install documentation
- build with verbose to see the compiler cmdlines</changelog>
  <changelog author="mrueckert@suse.de" date="1300536002">- moved binaries to _sbindir
- added init script
- added user and group
- added pgbouncer-1.4_default_config.patch
  change path for pid file and log file
- create log file in %install for proper permissions
- added logrotate file</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- fix build on older sle versions</changelog>
  <changelog author="mrueckert@suse.de" date="1302782401">- revert it, libevent is too old even on sle10</changelog>
  <changelog author="mrueckert@suse.de" date="1354017600">- update to 1.5.3: (CVE-2012-4575)
  see /usr/share/doc/packages/pgbouncer/NEWS
- drop pgbouncer-1.4_default_config.patch:
  applied upstream</changelog>
  <changelog author="darin@darins.net" date="1362744000">- Update to 1.5.4
  * DNS: Fix memory leak in getaddrinfo_a() backend.
  * DNS: Fix memory leak in udns backend.
  * DNS: Fix stats calculation.
  * DNS: Improve error message handling for getaddrinfo_a().
  * Fix win32 compile.
  * Fix compiler dependency support check in configure.
  * Few documentation fixes.</changelog>
  <changelog author="adam@mizerski.pl" date="1371556800">- fixed creation of system user</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 1.7.2
  all changes inbetween:
  https://pgbouncer.github.io/changelog.html#pgbouncer-17x
  https://pgbouncer.github.io/changelog.html#pgbouncer-16x
  https://pgbouncer.github.io/changelog.html#pgbouncer-15x</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- they use methods now that require openssl 1.0</changelog>
  <changelog author="mrueckert@suse.de" date="1467892801">- pull 3 patches from upstream:
  0001-tls-do-not-ask-TLS-on-unix-socket.patch
  0002-tls-reject-client-TLS-request-on-unix-socket.patch
  0003-hba-Skip-unparseable-lines-keep-parsing-to-the-end.patch
- fix service file reload action</changelog>
</package>
<package pkgid="ed4675bd5ab1f6cd363c5bfc820d7b370b05cf84a76f1b7a9d66109c94744745" name="pgbouncer-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.7.2" rel="3.2"/>
  <changelog author="mrueckert@suse.de" date="1300536000">- initial package (v1.4)</changelog>
  <changelog author="mrueckert@suse.de" date="1300536001">- install documentation
- build with verbose to see the compiler cmdlines</changelog>
  <changelog author="mrueckert@suse.de" date="1300536002">- moved binaries to _sbindir
- added init script
- added user and group
- added pgbouncer-1.4_default_config.patch
  change path for pid file and log file
- create log file in %install for proper permissions
- added logrotate file</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- fix build on older sle versions</changelog>
  <changelog author="mrueckert@suse.de" date="1302782401">- revert it, libevent is too old even on sle10</changelog>
  <changelog author="mrueckert@suse.de" date="1354017600">- update to 1.5.3: (CVE-2012-4575)
  see /usr/share/doc/packages/pgbouncer/NEWS
- drop pgbouncer-1.4_default_config.patch:
  applied upstream</changelog>
  <changelog author="darin@darins.net" date="1362744000">- Update to 1.5.4
  * DNS: Fix memory leak in getaddrinfo_a() backend.
  * DNS: Fix memory leak in udns backend.
  * DNS: Fix stats calculation.
  * DNS: Improve error message handling for getaddrinfo_a().
  * Fix win32 compile.
  * Fix compiler dependency support check in configure.
  * Few documentation fixes.</changelog>
  <changelog author="adam@mizerski.pl" date="1371556800">- fixed creation of system user</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 1.7.2
  all changes inbetween:
  https://pgbouncer.github.io/changelog.html#pgbouncer-17x
  https://pgbouncer.github.io/changelog.html#pgbouncer-16x
  https://pgbouncer.github.io/changelog.html#pgbouncer-15x</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- they use methods now that require openssl 1.0</changelog>
  <changelog author="mrueckert@suse.de" date="1467892801">- pull 3 patches from upstream:
  0001-tls-do-not-ask-TLS-on-unix-socket.patch
  0002-tls-reject-client-TLS-request-on-unix-socket.patch
  0003-hba-Skip-unparseable-lines-keep-parsing-to-the-end.patch
- fix service file reload action</changelog>
</package>
<package pkgid="e0d88f286f88aaab7506943f0d17f61b94ecf0c09f33917de723c694f5dc0883" name="pgbouncer-debugsource" arch="x86_64">
  <version epoch="0" ver="1.7.2" rel="3.2"/>
  <changelog author="mrueckert@suse.de" date="1300536000">- initial package (v1.4)</changelog>
  <changelog author="mrueckert@suse.de" date="1300536001">- install documentation
- build with verbose to see the compiler cmdlines</changelog>
  <changelog author="mrueckert@suse.de" date="1300536002">- moved binaries to _sbindir
- added init script
- added user and group
- added pgbouncer-1.4_default_config.patch
  change path for pid file and log file
- create log file in %install for proper permissions
- added logrotate file</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- fix build on older sle versions</changelog>
  <changelog author="mrueckert@suse.de" date="1302782401">- revert it, libevent is too old even on sle10</changelog>
  <changelog author="mrueckert@suse.de" date="1354017600">- update to 1.5.3: (CVE-2012-4575)
  see /usr/share/doc/packages/pgbouncer/NEWS
- drop pgbouncer-1.4_default_config.patch:
  applied upstream</changelog>
  <changelog author="darin@darins.net" date="1362744000">- Update to 1.5.4
  * DNS: Fix memory leak in getaddrinfo_a() backend.
  * DNS: Fix memory leak in udns backend.
  * DNS: Fix stats calculation.
  * DNS: Improve error message handling for getaddrinfo_a().
  * Fix win32 compile.
  * Fix compiler dependency support check in configure.
  * Few documentation fixes.</changelog>
  <changelog author="adam@mizerski.pl" date="1371556800">- fixed creation of system user</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 1.7.2
  all changes inbetween:
  https://pgbouncer.github.io/changelog.html#pgbouncer-17x
  https://pgbouncer.github.io/changelog.html#pgbouncer-16x
  https://pgbouncer.github.io/changelog.html#pgbouncer-15x</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- they use methods now that require openssl 1.0</changelog>
  <changelog author="mrueckert@suse.de" date="1467892801">- pull 3 patches from upstream:
  0001-tls-do-not-ask-TLS-on-unix-socket.patch
  0002-tls-reject-client-TLS-request-on-unix-socket.patch
  0003-hba-Skip-unparseable-lines-keep-parsing-to-the-end.patch
- fix service file reload action</changelog>
</package>
<package pkgid="00535144cb2814d21337563ecf31a8be4df59708743d74b581abd85808ce3c92" name="pgloader" arch="src">
  <version epoch="0" ver="2.3.2" rel="3.2"/>
  <changelog author="Devrim Gunduz &lt;devrim@CommandPrompt.com&gt; 2.2.0-1" date="1182427200">- Initial packaging</changelog>
  <changelog author="Devrim Gunduz &lt;devrim@CommandPrompt.com&gt; 2.2.5-1" date="1200744000">- Update to 2.2.5</changelog>
  <changelog author="Devrim Gunduz &lt;devrim@CommandPrompt.com&gt; 2.2.6-1" date="1201867200">- Update to 2.2.6</changelog>
  <changelog author="Devrim Gunduz &lt;devrim@CommandPrompt.com&gt; 2.3.0-1" date="1207742400">- Update to 2.3.0
- Various spec file fixes</changelog>
  <changelog author="Devrim Gunduz &lt;devrim@CommandPrompt.com&gt; 2.3.1-1" date="1213531200">- Update to 2.3.1</changelog>
  <changelog author="Devrim Gunduz &lt;devrim@CommandPrompt.com&gt; 2.3.2-1" date="1248782400">- Update to 2.3.2</changelog>
  <changelog author="darin@darins.net" date="1324987200">- Adapted .spec for OpenSuSE
- moved %changelog to .changes file
- Added py_compile and fdupes
  http://en.opensuse.org/openSUSE:Packaging_Python#Byte_Compiled_Files</changelog>
  <changelog author="darin@darins.net" date="1324987201">- removed BuildArch
- fixed non-standard group
- added %build and python-base require</changelog>
  <changelog author="darin@darins.net" date="1324987202">- fixed non-standard usage of %doc</changelog>
</package>
<package pkgid="9bc602c157e97bb630cce92a38f49139d68e7a3bd946e927e2422d5f25df37b3" name="pgloader" arch="x86_64">
  <version epoch="0" ver="2.3.2" rel="3.2"/>
  <changelog author="Devrim Gunduz &lt;devrim@CommandPrompt.com&gt; 2.2.0-1" date="1182427200">- Initial packaging</changelog>
  <changelog author="Devrim Gunduz &lt;devrim@CommandPrompt.com&gt; 2.2.5-1" date="1200744000">- Update to 2.2.5</changelog>
  <changelog author="Devrim Gunduz &lt;devrim@CommandPrompt.com&gt; 2.2.6-1" date="1201867200">- Update to 2.2.6</changelog>
  <changelog author="Devrim Gunduz &lt;devrim@CommandPrompt.com&gt; 2.3.0-1" date="1207742400">- Update to 2.3.0
- Various spec file fixes</changelog>
  <changelog author="Devrim Gunduz &lt;devrim@CommandPrompt.com&gt; 2.3.1-1" date="1213531200">- Update to 2.3.1</changelog>
  <changelog author="Devrim Gunduz &lt;devrim@CommandPrompt.com&gt; 2.3.2-1" date="1248782400">- Update to 2.3.2</changelog>
  <changelog author="darin@darins.net" date="1324987200">- Adapted .spec for OpenSuSE
- moved %changelog to .changes file
- Added py_compile and fdupes
  http://en.opensuse.org/openSUSE:Packaging_Python#Byte_Compiled_Files</changelog>
  <changelog author="darin@darins.net" date="1324987201">- removed BuildArch
- fixed non-standard group
- added %build and python-base require</changelog>
  <changelog author="darin@darins.net" date="1324987202">- fixed non-standard usage of %doc</changelog>
</package>
<package pkgid="d346f23ee9c2a3019d1f3a4842c6183d9bd62bfd3589e87090326b50fef0af0e" name="pgperl" arch="src">
  <version epoch="0" ver="2.1.1" rel="2.2"/>
  <changelog author="max@suse.de" date="1044360000">- Renamed from postgresql-perl to pgperl.
- New: verson 2.0.2
- The sources of pgperl have been moved out of the postgresql core
  distribution, and so this becomes a package of it's own. For
  older history see the changes file of the postgresql package.</changelog>
  <changelog author="max@suse.de" date="1046952000">- Added Provides and Obsoletes tags to document the rename.</changelog>
  <changelog author="ro@suse.de" date="1056369600">- added directory to filelist</changelog>
  <changelog author="ro@suse.de" date="1056628800">- removed traces of buildroot from installed files</changelog>
  <changelog author="max@suse.de" date="1058270400">- Fix build for perl-5.8.1.</changelog>
  <changelog author="mjancar@suse.cz" date="1061380800">- require the perl version we build with</changelog>
  <changelog author="adrian@suse.de" date="1073822400">- build as user</changelog>
  <changelog author="max@suse.de" date="1092916800">- New version: 2.1.1.</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- fix build on 11.4 and newer</changelog>
</package>
<package pkgid="68bdf23787cb914ddedcbe52676c5678e6192126259df55783afe4c04d47bd29" name="pgperl" arch="x86_64">
  <version epoch="0" ver="2.1.1" rel="2.2"/>
  <changelog author="max@suse.de" date="1044360000">- Renamed from postgresql-perl to pgperl.
- New: verson 2.0.2
- The sources of pgperl have been moved out of the postgresql core
  distribution, and so this becomes a package of it's own. For
  older history see the changes file of the postgresql package.</changelog>
  <changelog author="max@suse.de" date="1046952000">- Added Provides and Obsoletes tags to document the rename.</changelog>
  <changelog author="ro@suse.de" date="1056369600">- added directory to filelist</changelog>
  <changelog author="ro@suse.de" date="1056628800">- removed traces of buildroot from installed files</changelog>
  <changelog author="max@suse.de" date="1058270400">- Fix build for perl-5.8.1.</changelog>
  <changelog author="mjancar@suse.cz" date="1061380800">- require the perl version we build with</changelog>
  <changelog author="adrian@suse.de" date="1073822400">- build as user</changelog>
  <changelog author="max@suse.de" date="1092916800">- New version: 2.1.1.</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- fix build on 11.4 and newer</changelog>
</package>
<package pkgid="c3d8080894127d0f0834f0680f9c803cf820f4faafb2994d3f0c17a4bf5b927f" name="pgperl-debuginfo" arch="x86_64">
  <version epoch="0" ver="2.1.1" rel="2.2"/>
  <changelog author="max@suse.de" date="1044360000">- Renamed from postgresql-perl to pgperl.
- New: verson 2.0.2
- The sources of pgperl have been moved out of the postgresql core
  distribution, and so this becomes a package of it's own. For
  older history see the changes file of the postgresql package.</changelog>
  <changelog author="max@suse.de" date="1046952000">- Added Provides and Obsoletes tags to document the rename.</changelog>
  <changelog author="ro@suse.de" date="1056369600">- added directory to filelist</changelog>
  <changelog author="ro@suse.de" date="1056628800">- removed traces of buildroot from installed files</changelog>
  <changelog author="max@suse.de" date="1058270400">- Fix build for perl-5.8.1.</changelog>
  <changelog author="mjancar@suse.cz" date="1061380800">- require the perl version we build with</changelog>
  <changelog author="adrian@suse.de" date="1073822400">- build as user</changelog>
  <changelog author="max@suse.de" date="1092916800">- New version: 2.1.1.</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- fix build on 11.4 and newer</changelog>
</package>
<package pkgid="2bf6de4f85ee3d30a3455fc3c5af40a38549665f017e87d410a3fbacd9d06470" name="pgperl-debugsource" arch="x86_64">
  <version epoch="0" ver="2.1.1" rel="2.2"/>
  <changelog author="max@suse.de" date="1044360000">- Renamed from postgresql-perl to pgperl.
- New: verson 2.0.2
- The sources of pgperl have been moved out of the postgresql core
  distribution, and so this becomes a package of it's own. For
  older history see the changes file of the postgresql package.</changelog>
  <changelog author="max@suse.de" date="1046952000">- Added Provides and Obsoletes tags to document the rename.</changelog>
  <changelog author="ro@suse.de" date="1056369600">- added directory to filelist</changelog>
  <changelog author="ro@suse.de" date="1056628800">- removed traces of buildroot from installed files</changelog>
  <changelog author="max@suse.de" date="1058270400">- Fix build for perl-5.8.1.</changelog>
  <changelog author="mjancar@suse.cz" date="1061380800">- require the perl version we build with</changelog>
  <changelog author="adrian@suse.de" date="1073822400">- build as user</changelog>
  <changelog author="max@suse.de" date="1092916800">- New version: 2.1.1.</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="mrueckert@suse.de" date="1302782400">- fix build on 11.4 and newer</changelog>
</package>
<package pkgid="4d9c38d3951b9ea8810ccc93a3cd5b692ead1b2c6bd5c981237ea213fcd32ab4" name="pgpool-II" arch="src">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="9119114a4587dad089d71e918e3c88665d338dc64cf21f702b51c3976ba00c6c" name="pgpool-II" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="70ff49b3ef31208f5898f3da68b0bc702edb8e7db206a6f5c63787a32c8d1d79" name="pgpool-II-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="6a502ef0e9fe6c2cbffbd66e49847d44dc280ed659a86c64effa0152b1facd47" name="pgpool-II-debugsource" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="e35498c82add8cdfa2c196bd4d57969fa86e537649d05e26f2c0cf2f02d56773" name="pgpool-II-devel" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="d028f8c6ffb6990bd0062c61771c4baaaf1e23e6d549c109e7acd415e593ef2a" name="pgpoolAdmin" arch="x86_64">
  <version epoch="0" ver="3.5.3" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="02335e74d23bafe277fe9a4f9aebef2261ab8f2552bc8e7f8c0643c509b4ae4c" name="pgtune" arch="noarch">
  <version epoch="0" ver="0.9.3" rel="1.1"/>
  <changelog author="Greg Smith &lt;gsmith@gregsmith.com&gt; 0.9.2-1" date="1256731200">- Added copyright file, doesn't install sample postgresql.conf file.</changelog>
  <changelog author="Devrim Gunduz &lt;devrim@commandprompt.com&gt; 0.9.1-1" date="1256731201">- Initial packaging for PostgreSQL RPM Repository</changelog>
  <changelog author="darin@darins.net" date="1326715200">- Adapted spec to OpenSuSE
- added python-base requirement
- moved %changelog to .changes file</changelog>
</package>
<package pkgid="6be5aee38cda040ecf00e883a39b8a6328c5df7d222767fccc79ef09c78ae27f" name="pgtune" arch="src">
  <version epoch="0" ver="0.9.3" rel="1.1"/>
  <changelog author="Greg Smith &lt;gsmith@gregsmith.com&gt; 0.9.2-1" date="1256731200">- Added copyright file, doesn't install sample postgresql.conf file.</changelog>
  <changelog author="Devrim Gunduz &lt;devrim@commandprompt.com&gt; 0.9.1-1" date="1256731201">- Initial packaging for PostgreSQL RPM Repository</changelog>
  <changelog author="darin@darins.net" date="1326715200">- Adapted spec to OpenSuSE
- added python-base requirement
- moved %changelog to .changes file</changelog>
</package>
<package pkgid="0ae3b321af3dd267fb3414ad930dc3382d309c31dd6424024b4bb8293746b87a" name="pldebugger" arch="src">
  <version epoch="0" ver="9.4.git85d7b3b2" rel="1.4"/>
  <changelog author="kkaempf@suse.com" date="1438776000">- Initial version</changelog>
</package>
<package pkgid="c79e4b5aa3d783ab06b472e2b29e5c8905a34f85a871a3a20a2fd146e0e7e17c" name="pldebugger" arch="x86_64">
  <version epoch="0" ver="9.4.git85d7b3b2" rel="1.4"/>
  <changelog author="kkaempf@suse.com" date="1438776000">- Initial version</changelog>
</package>
<package pkgid="542c3519b74bc658d91599ef8d8f53e56337ac7c407818e1fa88723b7a5c919e" name="pldebugger-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.4.git85d7b3b2" rel="1.4"/>
  <changelog author="kkaempf@suse.com" date="1438776000">- Initial version</changelog>
</package>
<package pkgid="aa14eafbc90c2dc284899d1b61575ee0cd134a8a1c57fbc809d0b8b7ffdbfa8b" name="pldebugger-debugsource" arch="x86_64">
  <version epoch="0" ver="9.4.git85d7b3b2" rel="1.4"/>
  <changelog author="kkaempf@suse.com" date="1438776000">- Initial version</changelog>
</package>
<package pkgid="d7ac7925abbfa66f45e869ceb7ba45af03ec85afac7968c72d1a9508765c5f17" name="postgres-xl92" arch="src">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="df71ee3ea97363961816e686904bb756009f93ea12f990e1147d29ac06143814" name="postgres-xl92" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="149683a1d43f9d85233908454c08949f79d581170acc2427d070e0968320188c" name="postgres-xl92-contrib" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="952061cbce1d50c0b98697f10581d54d94119a1b2ad628325abd43ca7bd0e2f9" name="postgres-xl92-contrib-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="fb62a0eec23b1ecb62edaa3f48f05e1bf7f0b1c7fe61eff9fbe631d941bf49b1" name="postgres-xl92-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="1eff1c264d59408b84b308ea21cb4e99db7249d0b795a7181bf60152caf0c037" name="postgres-xl92-debugsource" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="9a3c83466fcd7e386f51969eb819ceccdd2e4e5e2661a3b394270fe96b93f30e" name="postgres-xl92-devel" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="12d602bc35e326ccc3d857a6826367d23406f93e9ce8052fccc22d01e32d723f" name="postgres-xl92-devel-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="11d9888b68502acc18c357cdb0900c5dd3b7905a0f26bc78a2d47bc43935bfd9" name="postgres-xl92-docs" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="efe6e5d988998f78c2ed7b7923fec44ded12287f829ee41e8aeeea0372e091be" name="postgres-xl92-gtm" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="29bdad6618fcc0ec3919f99c07015465c1216100c83dcde0423f5bf3c9176918" name="postgres-xl92-gtm-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="22bfc9cfceea0e71345aefda744f203bdc8fb527ec5c762cd766a897447faf0a" name="postgres-xl92-libs" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="de91a1519c1ba9392c5fea5975340ab464a8fd9227fc4cfd8aaa1e5976b8a538" name="postgres-xl92-libs-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="1481059b60f236a8ad03e56ee717e60895ef9994dda49cdc916fab7c453227a8" name="postgres-xl92-plperl" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="29f4c4b030b1f1746244f9d131502b8738af39b3a8dd97322706f29abf438ad1" name="postgres-xl92-plperl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="3443c98c6d156d424e374911ba9f9f242891cd5305406b9ef13cd858065678e0" name="postgres-xl92-plpython" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="36340c06e6f21b231452086b8f6410bd9a7dd35e9a9924caa59f4ab06d2e21f0" name="postgres-xl92-plpython-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="fbf5fc5ef05258a398e4a7c9471cac0d7a447d8a2f2caf4726641b32fd5c1a9c" name="postgres-xl92-pltcl" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="2a5206aedc0e85a09d453caf9b93f02ec14310230ee911c8afe54b61f0d5122a" name="postgres-xl92-pltcl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="68a998aaa0d69c4f1499011520a5c6abdff3bd77b768ba43d2273e6a6c5c0299" name="postgres-xl92-server" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="03497dc20d4a87ca318b98222fa0fd0eb56c31117c80e7b05fc14e829fd2346e" name="postgres-xl92-server-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2" rel="1.51"/>
  <changelog author="devrim@gunduz.org" date="1344859200">- Initial cut for 1.0.0</changelog>
  <changelog author="devrim@gunduz.org" date="1346673600">- Remove useless ldconfig call from -server subpackage.</changelog>
  <changelog author="devrim@gunduz.org" date="1346846400">- Update to 1.0.1</changelog>
  <changelog author="vivek.r@stormdb.com" date="1368964800">- Updated to 1.0.2</changelog>
  <changelog author="darin@darins.net" date="1406635200">- initial packaging for openSUSE</changelog>
  <changelog author="darin@darins.net" date="1407844800">- use standard header
- set Release to 0
- remove uid check
- %configure
- create %check and move %runselftest %test within
- removed %clean and %buildroot remove
- imported various defines, update-alternatives, from postgresl93
  spec</changelog>
</package>
<package pkgid="22270676eea2534b1fd4dd347da38b3ade98947a195c43ead98912bcc9785015" name="postgresql" arch="noarch">
  <version epoch="0" ver="9.6" rel="1.1"/>
  <changelog author="max@suse.com" date="1349092800">- Reduce the postgresql packages with unversioned names to dummy
  packages that require the respective versioned package names.</changelog>
  <changelog author="max@suse.com" date="1349352000">- Make PostgreSQL 9.2 the default.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Make all dummy packages noarch.</changelog>
  <changelog author="max@suse.com" date="1357732800">- Change license string to PostgreSQL.</changelog>
  <changelog author="max@suse.com" date="1379419200">- Bump version and defaultpackage to 9.3.</changelog>
  <changelog author="max@suse.com" date="1424260800">- Bump version and defaultpackage to 9.4.</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- Bump version and defaultpackage to 9.6.</changelog>
</package>
<package pkgid="ec55fd7a3683ef6ad7f73c4ff235a580b19f425ff64399d60a0a141a15726f38" name="postgresql" arch="src">
  <version epoch="0" ver="9.6" rel="1.1"/>
  <changelog author="max@suse.com" date="1349092800">- Reduce the postgresql packages with unversioned names to dummy
  packages that require the respective versioned package names.</changelog>
  <changelog author="max@suse.com" date="1349352000">- Make PostgreSQL 9.2 the default.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Make all dummy packages noarch.</changelog>
  <changelog author="max@suse.com" date="1357732800">- Change license string to PostgreSQL.</changelog>
  <changelog author="max@suse.com" date="1379419200">- Bump version and defaultpackage to 9.3.</changelog>
  <changelog author="max@suse.com" date="1424260800">- Bump version and defaultpackage to 9.4.</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- Bump version and defaultpackage to 9.6.</changelog>
</package>
<package pkgid="30aff1f507a58a2f33e3452c7ad2aee49c04fbadfc493d1634b8f6546ef1e8c0" name="postgresql-contrib" arch="noarch">
  <version epoch="0" ver="9.6" rel="1.1"/>
  <changelog author="max@suse.com" date="1349092800">- Reduce the postgresql packages with unversioned names to dummy
  packages that require the respective versioned package names.</changelog>
  <changelog author="max@suse.com" date="1349352000">- Make PostgreSQL 9.2 the default.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Make all dummy packages noarch.</changelog>
  <changelog author="max@suse.com" date="1357732800">- Change license string to PostgreSQL.</changelog>
  <changelog author="max@suse.com" date="1379419200">- Bump version and defaultpackage to 9.3.</changelog>
  <changelog author="max@suse.com" date="1424260800">- Bump version and defaultpackage to 9.4.</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- Bump version and defaultpackage to 9.6.</changelog>
</package>
<package pkgid="eba7a7e4fe780e285efeed93aafb8653a886f813b6c3058ffcf3427c8db4a3dc" name="postgresql-devel" arch="noarch">
  <version epoch="0" ver="9.6" rel="1.1"/>
  <changelog author="max@suse.com" date="1349092800">- Reduce the postgresql packages with unversioned names to dummy
  packages that require the respective versioned package names.</changelog>
  <changelog author="max@suse.com" date="1349352000">- Make PostgreSQL 9.2 the default.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Make all dummy packages noarch.</changelog>
  <changelog author="max@suse.com" date="1357732800">- Change license string to PostgreSQL.</changelog>
  <changelog author="max@suse.com" date="1379419200">- Bump version and defaultpackage to 9.3.</changelog>
  <changelog author="max@suse.com" date="1424260800">- Bump version and defaultpackage to 9.4.</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- Bump version and defaultpackage to 9.6.</changelog>
</package>
<package pkgid="274d00da46e6d010d869a3efa7969b7850352c1ff0b0fe1c7b67f29105423be2" name="postgresql-docs" arch="noarch">
  <version epoch="0" ver="9.6" rel="1.1"/>
  <changelog author="max@suse.com" date="1349092800">- Reduce the postgresql packages with unversioned names to dummy
  packages that require the respective versioned package names.</changelog>
  <changelog author="max@suse.com" date="1349352000">- Make PostgreSQL 9.2 the default.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Make all dummy packages noarch.</changelog>
  <changelog author="max@suse.com" date="1357732800">- Change license string to PostgreSQL.</changelog>
  <changelog author="max@suse.com" date="1379419200">- Bump version and defaultpackage to 9.3.</changelog>
  <changelog author="max@suse.com" date="1424260800">- Bump version and defaultpackage to 9.4.</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- Bump version and defaultpackage to 9.6.</changelog>
</package>
<package pkgid="279d6dc2b393e4a0a67a163647f8eca16a08d0b13ab3c41d04bde9647f8b0772" name="postgresql-init" arch="noarch">
  <version epoch="0" ver="9.6" rel="66.1"/>
  <changelog author="max@suse.com" date="1344340800">- Don't install the firewall script in place of the sysconfig
  template.</changelog>
  <changelog author="max@suse.com" date="1344600000">- Let the init script always use the private dir for existing
  databases, so that it doesn't fail when the active version
  has no server package installed (bnc#775402).
- Make the init script more verbose when things go wrong because
  of missing or non-matching server binaries.
- Let pg_ctl and the server process write to stdout again, so
  that it is easier to find out what happened if start failed.
- Make sure the init package doesn't get installed together with
  an old server package (bnc#775399).
- Add %stop_on_removal in case the init script gets uninstalled
  before the server as RPM dependencies don't seem to be enough to
  ensure this.</changelog>
  <changelog author="max@suse.com" date="1346241600">- Don't remove stale PID files and local sockets. PostgreSQL does
  not need it anymore, and the way it was done sometimes caused
  false removals (bnc#777797).</changelog>
  <changelog author="max@suse.com" date="1348660800">- Write postmaster output to a log file, so that processes starting
  PostgreSQL in a pipe don't hang (bnc#779927, bnc#780978).</changelog>
  <changelog author="max@suse.com" date="1348833600">- Run systemctl daemon_reload in %post and %postun</changelog>
  <changelog author="max@suse.com" date="1349352000">- Bump version to 9.2 to be in sync with the postgresql package.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Fix path and naming of fierewall script for SLE10.</changelog>
  <changelog author="max@suse.com" date="1374062400">- "ident sameuser" was already gone in 8.4.</changelog>
  <changelog author="max@suse.com" date="1378900800">- Bump version number to 9.3 to be dependency compatible with the
  latest PostgreSQL version.</changelog>
  <changelog author="meissner@suse.com" date="1406808000">- no need to directly require SuSEfirewall2 for the service,
  just also own the directory. (avoid massive rebuilds for SUSEfirewall2
  changes).</changelog>
  <changelog author="ro@suse.de" date="1409745600">- sanitize release line in specfile</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- bump version so it can bue used with 9.4</changelog>
  <changelog author="mrueckert@suse.de" date="1423742401">- do not own directories which are already owned by the filesystem
  package</changelog>
  <changelog author="max@suse.com" date="1444651200">- Move systemd related stuff and user/group creation from
  postgresqlXX-server to postgresql-init.</changelog>
  <changelog author="max@suse.com" date="1454414400">- Change the permissions and ownership of /var/run/postgresql to
  match those of /tmp (the traditional location of PostgreSQL's
  unix domain sockets and lock files), so that users other than
  "postgres" are able to start teir own database instances.</changelog>
  <changelog author="max@suse.com" date="1455537600">- Increase the default timeout for pg_ctl from 60 to 600 seconds
  and make it configurable (bsc#966285).</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- fix building on sle11:
  - guard all systemd related parts with build conditional
  - do not own fwdir on sle11</changelog>
  <changelog author="mrueckert@suse.de" date="1463832000">- bump to 9.6 so we can also build for the latest version</changelog>
  <changelog author="mrueckert@suse.de" date="1463832001">- fix building on 13.1 by removing the BuildRequires on systemd
  we will get it via systemd mini and the systemd_requires macro</changelog>
  <changelog author="kukuk@suse.de" date="1487419200">- Fix location of insserv cleanup call</changelog>
</package>
<package pkgid="bd791778da1e58f13c9f4c7549cb278b829de7a81efbbb1029fb97831bdba9de" name="postgresql-init" arch="src">
  <version epoch="0" ver="9.6" rel="66.1"/>
  <changelog author="max@suse.com" date="1344340800">- Don't install the firewall script in place of the sysconfig
  template.</changelog>
  <changelog author="max@suse.com" date="1344600000">- Let the init script always use the private dir for existing
  databases, so that it doesn't fail when the active version
  has no server package installed (bnc#775402).
- Make the init script more verbose when things go wrong because
  of missing or non-matching server binaries.
- Let pg_ctl and the server process write to stdout again, so
  that it is easier to find out what happened if start failed.
- Make sure the init package doesn't get installed together with
  an old server package (bnc#775399).
- Add %stop_on_removal in case the init script gets uninstalled
  before the server as RPM dependencies don't seem to be enough to
  ensure this.</changelog>
  <changelog author="max@suse.com" date="1346241600">- Don't remove stale PID files and local sockets. PostgreSQL does
  not need it anymore, and the way it was done sometimes caused
  false removals (bnc#777797).</changelog>
  <changelog author="max@suse.com" date="1348660800">- Write postmaster output to a log file, so that processes starting
  PostgreSQL in a pipe don't hang (bnc#779927, bnc#780978).</changelog>
  <changelog author="max@suse.com" date="1348833600">- Run systemctl daemon_reload in %post and %postun</changelog>
  <changelog author="max@suse.com" date="1349352000">- Bump version to 9.2 to be in sync with the postgresql package.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Fix path and naming of fierewall script for SLE10.</changelog>
  <changelog author="max@suse.com" date="1374062400">- "ident sameuser" was already gone in 8.4.</changelog>
  <changelog author="max@suse.com" date="1378900800">- Bump version number to 9.3 to be dependency compatible with the
  latest PostgreSQL version.</changelog>
  <changelog author="meissner@suse.com" date="1406808000">- no need to directly require SuSEfirewall2 for the service,
  just also own the directory. (avoid massive rebuilds for SUSEfirewall2
  changes).</changelog>
  <changelog author="ro@suse.de" date="1409745600">- sanitize release line in specfile</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- bump version so it can bue used with 9.4</changelog>
  <changelog author="mrueckert@suse.de" date="1423742401">- do not own directories which are already owned by the filesystem
  package</changelog>
  <changelog author="max@suse.com" date="1444651200">- Move systemd related stuff and user/group creation from
  postgresqlXX-server to postgresql-init.</changelog>
  <changelog author="max@suse.com" date="1454414400">- Change the permissions and ownership of /var/run/postgresql to
  match those of /tmp (the traditional location of PostgreSQL's
  unix domain sockets and lock files), so that users other than
  "postgres" are able to start teir own database instances.</changelog>
  <changelog author="max@suse.com" date="1455537600">- Increase the default timeout for pg_ctl from 60 to 600 seconds
  and make it configurable (bsc#966285).</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- fix building on sle11:
  - guard all systemd related parts with build conditional
  - do not own fwdir on sle11</changelog>
  <changelog author="mrueckert@suse.de" date="1463832000">- bump to 9.6 so we can also build for the latest version</changelog>
  <changelog author="mrueckert@suse.de" date="1463832001">- fix building on 13.1 by removing the BuildRequires on systemd
  we will get it via systemd mini and the systemd_requires macro</changelog>
  <changelog author="kukuk@suse.de" date="1487419200">- Fix location of insserv cleanup call</changelog>
</package>
<package pkgid="14c592a6f5124eea2c5b50e3e3f17eb0b66e80325697b03799895bc198bb5e58" name="postgresql-jdbc" arch="noarch">
  <version epoch="0" ver="9.4" rel="24.21"/>
  <changelog author="vlado.paskov@gmail.com" date="1299153600">- Initial package release.</changelog>
  <changelog author="darin@darins.net" date="1361448000">- Update to 9.2
- cleaned up .spec
- moved %changelog to .changes</changelog>
  <changelog author="darin@darins.net" date="1364299200">- Update license
- rpmlint cleanup</changelog>
  <changelog author="darin@darins.net" date="1364472000">- Set the correct license</changelog>
  <changelog author="tchvatal@suse.com" date="1378728000">- Move from jpackage-utils to javapackage-tools</changelog>
  <changelog author="tchvatal@suse.com" date="1403870400">- Version bump to latest release 9.3:
  * Various fixes
  * Better integration with pgsql9.3
- Cleanup with spec-cleaner</changelog>
  <changelog author="tchvatal@suse.com" date="1403870401">- Fix build on SLE11</changelog>
  <changelog author="tchvatal@suse.com" date="1404820800">- Do not depend on ant-trax.</changelog>
  <changelog author="tchvatal@suse.com" date="1405080000">- Do not version java docdir.</changelog>
  <changelog author="dmacvicar@suse.de" date="1436184000">- update to version 9.4-1200 (fate#318788)
  * https://jdbc.postgresql.org/documentation/changelog.html
- Add patch:
  * jdbc-postgresql-9.4_p1201-remove-sspi.patch</changelog>
</package>
<package pkgid="7a1147e14318b881be61d8f0d0890d0398decd6f23727eb701afe2db422d48ab" name="postgresql-jdbc" arch="src">
  <version epoch="0" ver="9.4" rel="24.21"/>
  <changelog author="vlado.paskov@gmail.com" date="1299153600">- Initial package release.</changelog>
  <changelog author="darin@darins.net" date="1361448000">- Update to 9.2
- cleaned up .spec
- moved %changelog to .changes</changelog>
  <changelog author="darin@darins.net" date="1364299200">- Update license
- rpmlint cleanup</changelog>
  <changelog author="darin@darins.net" date="1364472000">- Set the correct license</changelog>
  <changelog author="tchvatal@suse.com" date="1378728000">- Move from jpackage-utils to javapackage-tools</changelog>
  <changelog author="tchvatal@suse.com" date="1403870400">- Version bump to latest release 9.3:
  * Various fixes
  * Better integration with pgsql9.3
- Cleanup with spec-cleaner</changelog>
  <changelog author="tchvatal@suse.com" date="1403870401">- Fix build on SLE11</changelog>
  <changelog author="tchvatal@suse.com" date="1404820800">- Do not depend on ant-trax.</changelog>
  <changelog author="tchvatal@suse.com" date="1405080000">- Do not version java docdir.</changelog>
  <changelog author="dmacvicar@suse.de" date="1436184000">- update to version 9.4-1200 (fate#318788)
  * https://jdbc.postgresql.org/documentation/changelog.html
- Add patch:
  * jdbc-postgresql-9.4_p1201-remove-sspi.patch</changelog>
</package>
<package pkgid="86f72080a636344550c278ab1df436465b7450abadc22a9f851a7705aa450290" name="postgresql-jdbc-javadoc" arch="noarch">
  <version epoch="0" ver="9.4" rel="24.21"/>
  <changelog author="vlado.paskov@gmail.com" date="1299153600">- Initial package release.</changelog>
  <changelog author="darin@darins.net" date="1361448000">- Update to 9.2
- cleaned up .spec
- moved %changelog to .changes</changelog>
  <changelog author="darin@darins.net" date="1364299200">- Update license
- rpmlint cleanup</changelog>
  <changelog author="darin@darins.net" date="1364472000">- Set the correct license</changelog>
  <changelog author="tchvatal@suse.com" date="1378728000">- Move from jpackage-utils to javapackage-tools</changelog>
  <changelog author="tchvatal@suse.com" date="1403870400">- Version bump to latest release 9.3:
  * Various fixes
  * Better integration with pgsql9.3
- Cleanup with spec-cleaner</changelog>
  <changelog author="tchvatal@suse.com" date="1403870401">- Fix build on SLE11</changelog>
  <changelog author="tchvatal@suse.com" date="1404820800">- Do not depend on ant-trax.</changelog>
  <changelog author="tchvatal@suse.com" date="1405080000">- Do not version java docdir.</changelog>
  <changelog author="dmacvicar@suse.de" date="1436184000">- update to version 9.4-1200 (fate#318788)
  * https://jdbc.postgresql.org/documentation/changelog.html
- Add patch:
  * jdbc-postgresql-9.4_p1201-remove-sspi.patch</changelog>
</package>
<package pkgid="d91f2eb9a10d8a8ed1625050c3cad03c1025772d905a29f9b5b3a5e90d2afbd9" name="postgresql-pgfincore" arch="src">
  <version epoch="0" ver="1.1.2" rel="4.2"/>
  <changelog author="lars@linux-schulserver.de" date="1417435200">- initial version 1.1.2</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- fix build by using the proper paths</changelog>
  <changelog author="max@suse.com" date="1424433600">- We are a server extension, so require the -server instead of the
  main package.</changelog>
</package>
<package pkgid="0da5e86d50391ea94a9a8ca6262b57617c9e856c9487dbb02f78a6d072b3cbd3" name="postgresql-pgfincore" arch="x86_64">
  <version epoch="0" ver="1.1.2" rel="4.2"/>
  <changelog author="lars@linux-schulserver.de" date="1417435200">- initial version 1.1.2</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- fix build by using the proper paths</changelog>
  <changelog author="max@suse.com" date="1424433600">- We are a server extension, so require the -server instead of the
  main package.</changelog>
</package>
<package pkgid="519e000d40fc0a4c368432d9a8710c3f2ad5bb3b835495d6f5cf465df26accb5" name="postgresql-pgfincore" arch="src">
  <version epoch="0" ver="1.1.2" rel="6.4"/>
  <changelog author="lars@linux-schulserver.de" date="1417435200">- initial version 1.1.2</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- fix build by using the proper paths</changelog>
  <changelog author="max@suse.com" date="1424433600">- We are a server extension, so require the -server instead of the
  main package.</changelog>
</package>
<package pkgid="f5d8808041704e4d709d7d6df13a85d839671f8045f869e37366a1a0345751c9" name="postgresql-pgfincore" arch="x86_64">
  <version epoch="0" ver="1.1.2" rel="6.4"/>
  <changelog author="lars@linux-schulserver.de" date="1417435200">- initial version 1.1.2</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- fix build by using the proper paths</changelog>
  <changelog author="max@suse.com" date="1424433600">- We are a server extension, so require the -server instead of the
  main package.</changelog>
</package>
<package pkgid="2e32b05938944cca9822172b836249a70001a97f28a7d292ce6e9246719e4c41" name="postgresql-pgfincore-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.1.2" rel="4.2"/>
  <changelog author="lars@linux-schulserver.de" date="1417435200">- initial version 1.1.2</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- fix build by using the proper paths</changelog>
  <changelog author="max@suse.com" date="1424433600">- We are a server extension, so require the -server instead of the
  main package.</changelog>
</package>
<package pkgid="92a7eaa77202461ae89f8d01b69c894fdeda79faea54bcbb7474de742ae94106" name="postgresql-pgfincore-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.1.2" rel="6.4"/>
  <changelog author="lars@linux-schulserver.de" date="1417435200">- initial version 1.1.2</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- fix build by using the proper paths</changelog>
  <changelog author="max@suse.com" date="1424433600">- We are a server extension, so require the -server instead of the
  main package.</changelog>
</package>
<package pkgid="fe88566445df51a398a610504661a8d440aa847e6ae64dd0dd5dfbe5fb901580" name="postgresql-pgfincore-debugsource" arch="x86_64">
  <version epoch="0" ver="1.1.2" rel="4.2"/>
  <changelog author="lars@linux-schulserver.de" date="1417435200">- initial version 1.1.2</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- fix build by using the proper paths</changelog>
  <changelog author="max@suse.com" date="1424433600">- We are a server extension, so require the -server instead of the
  main package.</changelog>
</package>
<package pkgid="4b5b02c35ebc271478411db10d3f94e732d58e6fa9ed0adf587ce7cbfca52a40" name="postgresql-pgfincore-debugsource" arch="x86_64">
  <version epoch="0" ver="1.1.2" rel="6.4"/>
  <changelog author="lars@linux-schulserver.de" date="1417435200">- initial version 1.1.2</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- fix build by using the proper paths</changelog>
  <changelog author="max@suse.com" date="1424433600">- We are a server extension, so require the -server instead of the
  main package.</changelog>
</package>
<package pkgid="4c2c0d1cd682a90041549934ed1183eca151c99fc7e73cffbe8c00a27ddf66fd" name="postgresql-plperl" arch="noarch">
  <version epoch="0" ver="9.6" rel="1.1"/>
  <changelog author="max@suse.com" date="1349092800">- Reduce the postgresql packages with unversioned names to dummy
  packages that require the respective versioned package names.</changelog>
  <changelog author="max@suse.com" date="1349352000">- Make PostgreSQL 9.2 the default.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Make all dummy packages noarch.</changelog>
  <changelog author="max@suse.com" date="1357732800">- Change license string to PostgreSQL.</changelog>
  <changelog author="max@suse.com" date="1379419200">- Bump version and defaultpackage to 9.3.</changelog>
  <changelog author="max@suse.com" date="1424260800">- Bump version and defaultpackage to 9.4.</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- Bump version and defaultpackage to 9.6.</changelog>
</package>
<package pkgid="63e063e0d38f5eddef8cdc7d35e456b9e7307dd81852d214bffcc3685430d377" name="postgresql-plpython" arch="noarch">
  <version epoch="0" ver="9.6" rel="1.1"/>
  <changelog author="max@suse.com" date="1349092800">- Reduce the postgresql packages with unversioned names to dummy
  packages that require the respective versioned package names.</changelog>
  <changelog author="max@suse.com" date="1349352000">- Make PostgreSQL 9.2 the default.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Make all dummy packages noarch.</changelog>
  <changelog author="max@suse.com" date="1357732800">- Change license string to PostgreSQL.</changelog>
  <changelog author="max@suse.com" date="1379419200">- Bump version and defaultpackage to 9.3.</changelog>
  <changelog author="max@suse.com" date="1424260800">- Bump version and defaultpackage to 9.4.</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- Bump version and defaultpackage to 9.6.</changelog>
</package>
<package pkgid="e1c2672addba1b793799bf3705f0cfe119dfae57e497bdd36829f7b4fc0c7be8" name="postgresql-pltcl" arch="noarch">
  <version epoch="0" ver="9.6" rel="1.1"/>
  <changelog author="max@suse.com" date="1349092800">- Reduce the postgresql packages with unversioned names to dummy
  packages that require the respective versioned package names.</changelog>
  <changelog author="max@suse.com" date="1349352000">- Make PostgreSQL 9.2 the default.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Make all dummy packages noarch.</changelog>
  <changelog author="max@suse.com" date="1357732800">- Change license string to PostgreSQL.</changelog>
  <changelog author="max@suse.com" date="1379419200">- Bump version and defaultpackage to 9.3.</changelog>
  <changelog author="max@suse.com" date="1424260800">- Bump version and defaultpackage to 9.4.</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- Bump version and defaultpackage to 9.6.</changelog>
</package>
<package pkgid="cb8936459a560c06d8964ad951ec2df6894f98d6bae720be818867149f2729c9" name="postgresql-server" arch="noarch">
  <version epoch="0" ver="9.6" rel="1.1"/>
  <changelog author="max@suse.com" date="1349092800">- Reduce the postgresql packages with unversioned names to dummy
  packages that require the respective versioned package names.</changelog>
  <changelog author="max@suse.com" date="1349352000">- Make PostgreSQL 9.2 the default.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Make all dummy packages noarch.</changelog>
  <changelog author="max@suse.com" date="1357732800">- Change license string to PostgreSQL.</changelog>
  <changelog author="max@suse.com" date="1379419200">- Bump version and defaultpackage to 9.3.</changelog>
  <changelog author="max@suse.com" date="1424260800">- Bump version and defaultpackage to 9.4.</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- Bump version and defaultpackage to 9.6.</changelog>
</package>
<package pkgid="8243270614590fb4e549e0b995a116b8628e988ac859f19627089cd29c4f5b3d" name="postgresql91" arch="src">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="171c3d67e99b5aeca4f3be154a3da7432c0019588f68a1f36d8898ca12e9eebe" name="postgresql91" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="de14236e264f5f9bffdc532c8013291703bb1bc0d277c9cfc4c5ddbea40a74a6" name="postgresql91-contrib" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="f2b0f0c54f436d5041d48a72792e05f67e7d67ebf9c71b5f655f97a783904883" name="postgresql91-contrib-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="31d854673430985baf9e2c512d55113e5c3719f75880589c6485906e8d8556b1" name="postgresql91-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="ba1978181537fe20b60ea9184f8ce70982eea6880acc0ffea7a6cc9cd99ccb82" name="postgresql91-debugsource" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="24b1c0f58cc1f97b4d13e24b315ed5955330ba7fbf6a9b3da927994ce3958f3d" name="postgresql91-devel" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.1"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="a2906482d59fdf27737fdca13adb642907c9084503fb6f1b51984f9a4e2fb2d4" name="postgresql91-devel-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.1"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="a7a3c83e32615aa49df23278eb34c3a1b3aeeb00a779e96a0045744f4734b1dd" name="postgresql91-docs" arch="noarch">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="191a7c6890ceffe5cc8c95c94c466d05397c0a736daab7d3f662376897cf41c6" name="postgresql91-ip4r" arch="src">
  <version epoch="0" ver="2.0.2" rel="19.2"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="36cb21ea00cb72aea619868bdf2382eafd28cbdae22824d261406f709ecb86c4" name="postgresql91-ip4r" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.2"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="f5d2635e94f7d2435207d21513a62ee081ebd9c021f6ae9d95181aa43576f6bc" name="postgresql91-ip4r-debuginfo" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.2"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="4d0e04ea120fbc9668ff439b6c3503c3b5a37e3193ea6119c95acdb0705bec72" name="postgresql91-ip4r-debugsource" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.2"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="b1311e8752c70bbe9ea2963a1ebdefd25465a447007c73cd9773c61825274c82" name="postgresql91-libs" arch="src">
  <version epoch="0" ver="9.1.24" rel="1.1"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="378f0b1c980adb6066d501952689e4cca4ed642edb414bf93f70e4871ab9cd99" name="postgresql91-libs-debugsource" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.1"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="2a0a6d46f5bd492d271120219b92da471815145c0267d872ae97cb35d34510d7" name="postgresql91-orafce" arch="src">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.1-1" date="1186747200">- Update to 2.1.1
- Spec file cleanup</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-1" date="1200312000">- Update to 2.1.3</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-2" date="1200830400">- Spec file fixes, per bz review #251805</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.4-1" date="1219233600">- Update to 2.1.4</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="721dcc8c2f42de9f57dde587f324fda3ccf122892b1643ebc15d303413ca7939" name="postgresql91-orafce" arch="x86_64">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="5a14c30859f7b9bcef50e19a1ef6fd9714003f0158fc51e0f6d232f944416340" name="postgresql91-orafce-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.1-1" date="1186747200">- Update to 2.1.1
- Spec file cleanup</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-1" date="1200312000">- Update to 2.1.3</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-2" date="1200830400">- Spec file fixes, per bz review #251805</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.4-1" date="1219233600">- Update to 2.1.4</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="9840555ddc13d31a3ea70ea207ca3ca649b1722044dd97f981a37c2055ba1cd3" name="postgresql91-orafce-debugsource" arch="x86_64">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="d341974b2ee309e79cbe8b4ba1bffe05e74f1db2f939732db7a50fd8eacef430" name="postgresql91-plperl" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="95ceebb9b17855257970d131fe856d75e0768d04c3064a5db5d9e9f35b84acb2" name="postgresql91-plperl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="209f0e3c33c7c8a776db698af183bd79bd99e3f03cbf336657adb9a2a2431f58" name="postgresql91-plpython" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="f07dfd85b40bd81a8e0ebc6e0f932d4cab8b074260c1be6428125cab54052b3c" name="postgresql91-plpython-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="c989e4331ebab586f4c0f75d0252ca93b697f1a29d4643af6379d7722506f0ed" name="postgresql91-plr" arch="src">
  <version epoch="0" ver="8.3.0.17" rel="30.2"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="b4836d0f133862bd5b9a08e678bb6f84137133afbf130964be20f498f9af6876" name="postgresql91-plr" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="30.2"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="18dfbbe2c016cdd306eff1d0ab0084ac209e6d292ee82800f347816c560c1097" name="postgresql91-plr-debuginfo" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="30.2"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="c0fc60a34bd0097dacc449e466dc874ff581175453124d236d097bc3734b5296" name="postgresql91-plr-debugsource" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="30.2"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="4cbcc15b3fc5094deaa9a35090fbf4e9912a83c45e884d42057b7445cd23f045" name="postgresql91-plr-doc" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="30.2"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="acd77fd0c8807e374dd498c9b9d0a38d996777bbe5821604105f12ff9585e419" name="postgresql91-pltcl" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="1f438b80e6748dd221bc32d1aa3067441203c97316111e8c7bc07d55cf4197bb" name="postgresql91-pltcl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="af319c8793139df7f811d54ecef0fa2171f89a7a6ce38d026e070460dfa16e50" name="postgresql91-server" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="e269dbadd8cd830ecc6b270ad34f6f4e755a4369a451999f57c9258504dbe08d" name="postgresql91-server-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="b4fc94b6eef82924bb32d80b606846e234679b1fd634608e43e116901b5b0523" name="postgresql91-test" arch="x86_64">
  <version epoch="0" ver="9.1.24" rel="1.20"/>
  <changelog author="idonmez@novell.com" date="1306324800">- Add postgresql-9.0.4-perl514.patch: For Perl 5.14 GvCV(sv) is no
  longer an lvalue and needs to be replaced by GvCV_set(sv, value)</changelog>
  <changelog author="max@novell.com" date="1306324801">- Fix file name of last added patch and remove overlong comment.</changelog>
  <changelog author="max@novell.com" date="1307534400">- Revert the postgresql-libs package split for SLE in preparation
  of submitting the package to SLE11-SP1.</changelog>
  <changelog author="jengelh@medozas.de" date="1316174400">- Add postgresql-devel to baselibs</changelog>
  <changelog author="max@suse.com" date="1317816000">- New version 9.1.1. For detailed release notes, see:
  http://www.postgresql.org/docs/9.1/static/release-9-1-1.html
- Stop using deprecated silent_mode in default config.
- postgresql-perl514.patch is no longer needed.
- Use %_smp_mflags for parallel make
- Keep the rpath when linking plperl [bnc#578053].</changelog>
  <changelog author="max@suse.com" date="1331553600">- Security and bugfix release 9.1.3:
  * Require execute permission on the trigger function for "CREATE
    TRIGGER" (CVE-2012-0866, bnc#749299).
  * Remove arbitrary limitation on length of common name in SSL
    certificates (CVE-2012-0867, bnc#749301).
  * Convert newlines to spaces in names written in pg_dump
    comments (CVE-2012-0868, bnc#749303).
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY
- This also fixes bnc#701489.</changelog>
  <changelog author="zawel1@gmail.com" date="1347883200">- Security and bugfix release 9.1.5:
  * Ignore SECURITY DEFINER and SET attributes for a procedural
    language's call handler (CVE-2012-2655)
  * Fix incorrect password transformation in "contrib/pgcrypto"'s DES
    crypt() function (CVE-2012-2143)
  * Prevent access to external files/URLs via "contrib/xml2"'s
    xslt_process() (CVE-2012-3488)
  * Prevent access to external files/URLs via XML entity references
    (CVE-2012-3489)
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1349092800">- Bugfix release 9.1.6 (bnc#782251) to fix data corruption issues.
  * Users who upgrade from a previous 9.1 release should run
    REINDEX after applying this update.
    See also: http://wiki.postgresql.org/wiki/20120924updaterelease
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html
- Change the base name of all PostgreSQL packages from postgresql
  to postgresql91 and adopt the new packaging schema, which allows
  the parallel installation of multiple PostgreSQL versions to
  simplify and speedup migration.
- Move init script, sysconfig file and firewall configuration into
  a new package called postgresql-init which can work with
  different PostgreSQL versions.</changelog>
  <changelog author="max@suse.com" date="1349438400">- Resolve "have choice for libpq.so.5" by ignoring postgresql-libs.</changelog>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="max@suse.com" date="1356091200">- Bugfix release 9.1.7:
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * For the full list of changes, see
    http://www.postgresql.org/docs/9.1/static/release.html</changelog>
  <changelog author="max@suse.com" date="1360670400">- Updated to version 9.1.8:
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-8.html
    /usr/share/doc/packages/postgresql/HISTORY
- Exclude non-versioned postgtesql from buildrequires to fix build
  on SLE11 (bnc#803249).
- Remove postgresql91-full.spec.in and use postgresql91.spec as the
  master for generating postgresql91-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.1.9 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-9.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1379937600">- rpm doesn't understand != in package dependencies (bnc#841112)</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.1.11:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Fix incorrect generation of optimized MIN()/MAX() plans for
    inheritance trees
  * Prevent corruption of multi-byte characters when attempting
    to case-fold identifiers
  * Prevent pushing down WHERE clauses into unsafe UNION/INTERSECT
    subqueries
  * Properly guarantee transmission of WAL files before clean
    switchover
  * Loosen restriction on keywords used in queries
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-11.html
    /usr/share/doc/packages/postgresql91/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.1.12:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-12.html
- Fix handling of alternatives in the file lists.
- Fix license tags</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.1.15:
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.1/static/release-9-1-15.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.
- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.1.23:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-23.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.1.24:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * Remove artificial restrictions on the values accepted by
    numeric_in() and numeric_recv()
  * Avoid very-low-probability data corruption due to testing tuple
    visibility without holding buffer lock
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.1/static/release-9-1-24.html</changelog>
</package>
<package pkgid="a9647bd792ce72bdc5ab8cc76981e50fdf1c47f80fbc8014ef7c10d7d78b5bfc" name="postgresql92" arch="src">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="54bcbeee20589f326f889dcd945caba43f8ab6b8f6c5042191e77c645e0328b1" name="postgresql92" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="60b63c4d368150b8d84d78cf44e26b2c507f06b24043dff1174dcfa241220fef" name="postgresql92-contrib" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="0926ceed9f41f2b4d6f0e1d05717007b9c2c80a5cc5cdfa2ce8c47617f66899e" name="postgresql92-contrib-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="8d543d82684d250e8d0479e39bbb890aff3290a157f3e184b61bf9253e2460ba" name="postgresql92-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="861f8a11e30ece177a10af3cf708d47ca1c5d8cbfa36de44a4995db1f3a6ae86" name="postgresql92-debugsource" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="4912849f5428f9a7efd2408610f0d4236e9e8b1c7f2e76f79b64bc3b704a33b6" name="postgresql92-devel" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="3.1"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="96d40f54119192970cf30aed5a92bc298948ad6b8d841706b40888f58c5a0394" name="postgresql92-devel-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="3.1"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="eaff0f442603993a17807af9f8dea8ce32485e01c670028a3c9921628113ba9e" name="postgresql92-docs" arch="noarch">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="eed10a0a9bae5b5cc70adac3f6e8fc94a1bd121c52aba0c295b3d3201e1eb9fc" name="postgresql92-ip4r" arch="src">
  <version epoch="0" ver="2.0.2" rel="19.3"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="d5275aed575f43e38cf1d73b651f67a99c7b384375f82962458d4e5c93ba79c0" name="postgresql92-ip4r" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.3"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="9aa4e442c27fe78a679caa28349aec664dbd27837c9f3b97bedf6a101247545b" name="postgresql92-ip4r-debuginfo" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.3"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="3f493e47c66c8b97ee2694bfca0cd6c15c5a23534ae9344771954a0b78fb3d67" name="postgresql92-ip4r-debugsource" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.3"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="afa54cf67688252c033d01a5b745351a6f120f77e1a3d585ee60c6384afe6bea" name="postgresql92-libs" arch="src">
  <version epoch="0" ver="9.2.20" rel="3.1"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="1ba09c77620b25cb08220d6c07cdc5412df4d036572400d8cfe4b351c447a35e" name="postgresql92-libs-debugsource" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="3.1"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="c518e04959d6c67f706625b48180505a5a2ae9b84827c227e8a8cc365b7f60bc" name="postgresql92-orafce" arch="src">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.1-1" date="1186747200">- Update to 2.1.1
- Spec file cleanup</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-1" date="1200312000">- Update to 2.1.3</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-2" date="1200830400">- Spec file fixes, per bz review #251805</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.4-1" date="1219233600">- Update to 2.1.4</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="57e1e280d9152b8aa5ba1923a190fcde13733cb277be6f91f710d7cccec32caf" name="postgresql92-orafce" arch="x86_64">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="1c276bc8e53459b6a428eaebd884b0e1f8f9b7bc97115176cc8aa8a81019b4f8" name="postgresql92-orafce-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.1-1" date="1186747200">- Update to 2.1.1
- Spec file cleanup</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-1" date="1200312000">- Update to 2.1.3</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-2" date="1200830400">- Spec file fixes, per bz review #251805</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.4-1" date="1219233600">- Update to 2.1.4</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="3d3db417591a7c817c4071cb67bd9c1936748e4133cecf11135d43e471d34095" name="postgresql92-orafce-debugsource" arch="x86_64">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="87b43ceb1f977fe087d231e9d3ab63baee73062442952522b20573310744e2c7" name="postgresql92-plperl" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="cd2e7a93b7001dd754cb7681f8d4ef725be3ecf3be6522b703b775dbaab34b29" name="postgresql92-plperl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="9a2194acf95177ab11c9d1c551b0ce2c387e702d66c03f0fb71169cc597f9b47" name="postgresql92-plpython" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="feec44f1d44f01344a22485bdec4e0e07498be35001c708511c21bfe9310f394" name="postgresql92-plpython-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="3e0bfe54d9e0d94d83a8c2b3150c832a8343921bf9413cbf2d15738b3f2381b7" name="postgresql92-plr" arch="src">
  <version epoch="0" ver="8.3.0.17" rel="30.2"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="fe4aa568e03ae8da690937794c62aeffee0aa1fd05a2abb9b45ef0f4482a4fa7" name="postgresql92-plr" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="30.2"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="f17601c463f7491bc52eaa656004123b16e5f48ac67072dd2fb40366fba3dca0" name="postgresql92-plr-debuginfo" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="30.2"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="b1c2e9ed4546f85a1383eedcbe07fe802396dd13ee97f89341a620c1e90146d6" name="postgresql92-plr-debugsource" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="30.2"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="2287d81dda59eeb101ffb3627a39aa79a27f9387e916c9afd5caad2bb860d629" name="postgresql92-plr-doc" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="30.2"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="7ccafe61600222077364df18f198b37cc068efbf6e981399f980ad6cdbefd8d1" name="postgresql92-pltcl" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="258db2fac091ea02c96d698b9c9f4eecc658047a51192840e3dc380c8d680799" name="postgresql92-pltcl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="2689fd6e31f54deb29af1c54ee0983db022a3b7650d2cbd3f17609e2f6e083e4" name="postgresql92-server" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="f4886fd01774707c9fe1fba8bc356f1427e76faf817f3a57c67ba4a5cca59abb" name="postgresql92-server-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="6122a623a1ee11501b3c60df8292cbb25c65817d041e14c4660a35c3b093a856" name="postgresql92-test" arch="x86_64">
  <version epoch="0" ver="9.2.20" rel="1.15"/>
  <changelog author="max@suse.com" date="1353326400">- Change mechanism for making postgresql??-devel exclusive
  (bnc#789562).</changelog>
  <changelog author="darin@darins.net" date="1355400000">- Updated to version 9.2.2
  * Fix multiple bugs associated with
    CREATE/DROP INDEX CONCURRENTLY
  * Correct predicate locking for DROP INDEX CONCURRENTLY
  * Fix buffer locking during WAL replay
  * Fix an error in WAL generation logic for GIN indexes
  * Fix an error in WAL replay logic for SP-GiST indexes
  * Fix incorrect detection of end-of-base-backup location
    during WAL recovery
  * Properly remove startup process's virtual XID lock when
    promoting a hot standby server to normal running
  * Avoid bogus "out-of-sequence timeline ID" errors in standby
    mode
  * Prevent the postmaster from launching new child processes after
    it's received a shutdown signal
  * Fix the syslogger process to not fail when log_rotation_age
    exceeds 2^31 milliseconds
  * Fix WaitLatch() to return promptly when the requested timeout
    expires
  * Avoid corruption of internal hash tables when out of memory
  * Prevent file descriptors for dropped tables from being held
    open past transaction end
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-2.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1356004800">- Conflicts tags don't support the != operator.</changelog>
  <changelog author="max@suse.com" date="1357646400">- Use PDX license string.</changelog>
  <changelog author="darin@darins.net" date="1360324800">- Updated to version 9.2.3
  * Prevent execution of enum_recv from SQL (Tom Lane)
  * Fix multiple problems in detection of when a consistent database
    state has been reached during WAL replay
  * Fix detection of end-of-backup point when no actual redo
    work is required
  * Update minimum recovery point when truncating a relation file
  * Fix recycling of WAL segments after changing recovery target
    timeline
  * Properly restore timeline history files from archive on
    cascading standby servers
  * Fix lock conflict detection on hot-standby servers
  * Fix missing cancellations in hot standby mode
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-3.html
    /usr/share/doc/packages/postgresql/HISTORY</changelog>
  <changelog author="max@suse.com" date="1360756800">- Version 9.2.3 also fixes bnc#802679, CVE-2013-0255.
- Remove postgresql92-full.spec.in and use postgresql92.spec as the
  master for generating postgresql92-libs.spec.</changelog>
  <changelog author="max@suse.com" date="1364904000">- Updated to version 9.2.4 (bnc#812525):
  * CVE-2013-1899: Fix insecure parsing of server command-line
    switches. A connection request containing a database name that
    begins with "-" could be crafted to damage or destroy files
    within the server's data directory, even if the request is
    eventually rejected.
  * CVE-2013-1900: Reset OpenSSL randomness state in each
    postmaster child process. This avoids a scenario wherein
    random numbers generated by "contrib/pgcrypto" functions might
    be relatively easy for another database user to guess. The
    risk is only significant when the postmaster is configured
    with ssl = on but most connections don't use SSL encryption.
  * CVE-2013-1901: Make REPLICATION privilege checks test current
    user not authenticated user.  An unprivileged database user
    could exploit this mistake to call pg_start_backup() or
    pg_stop_backup(), thus possibly interfering with creation of
    routine backups.
  * See the release notes for the rest of the changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-4.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="idonmez@suse.com" date="1366027200">- Add Source URL, see https://en.opensuse.org/SourceUrls</changelog>
  <changelog author="schwab@suse.de" date="1368014400">- postgresql-tas-aarch64.patch: Implement TAS for aarch64</changelog>
  <changelog author="kpetsch@suse.com" date="1386331200">- Added option to build postgresql-devel package separatly from
  postresql-libs</changelog>
  <changelog author="kpetsch@suse.com" date="1386331201">- Update to version 9.2.6:
  * Fix VACUUM's tests to see whether it can update relfrozenxid
  * Fix initialization of pg_clog and og_subtrans during hot
    standby startup
  * Fix dangling-pointer problem in fast-path locking
  * Truncate pg_multixact contents during WAL replay
  * Fix race condition in GIN index posting tree page deletion
  * Prevent intra-transaction memory leak when printing range
    values
  * Fix incorrect behaviors when using a SQL-standard, simple GMT
    offset timezone
  * Prevent pushing down WHERE clauses into unsafe
    UNION/INTERSECT subqueries
  * Loosen restriction on keywords used in queries
  * Properly compute row estimates for boolean columns containing
    many NULL values
  * See release notes for a full list of changes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-6.html
    /usr/share/doc/packages/postgresql92/HISTORY</changelog>
  <changelog author="max@suse.com" date="1392984000">- Security and bugfix release 9.2.7:
  * Shore up GRANT ... WITH ADMIN OPTION restrictions
    (CVE-2014-0060, bnc#864845)
  * Prevent privilege escalation via manual calls to PL validator
    functions (CVE-2014-0061, bnc#864846)
  * Avoid multiple name lookups during table and index DDL
    (CVE-2014-0062, bnc#864847)
  * Prevent buffer overrun with long datetime strings
    (CVE-2014-0063, bnc#864850)
  * Prevent buffer overrun due to integer overflow in size
    calculations (CVE-2014-0064, bnc#864851)
  * Prevent overruns of fixed-size buffers (CVE-2014-0065,
    bnc#864852)
  * Avoid crashing if crypt() returns NULL (CVE-2014-0066,
    bnc#864853)
  * Document risks of make check in the regression testing
    instructions (CVE-2014-0067)
  * For the other (many!) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-2-7.html
    /usr/share/doc/packages/postgresql92/HISTORY
- Fix handling of alternatives in the file lists.</changelog>
  <changelog author="klaussfreire@gmail.com" date="1411732800">- Security and bugfix release 9.2.9:
  * Crash and corruption fixes for GiST and GIN
  * Various memory leaks fixed
  * pg_hba client hostname lookups fixed
  * Avoid DoS by induced bufferbloat in libpq
  * Fix pgcrypto functions to avoid leaving sensitive values
    on the stack after returning
  * Fix use-after-free in pgstat_heap()
  * For the other (many) bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-9.html
- Fixes from release 9.2.8:
  * Corruption fixes for GIN during replay of GIN metapage updates
  * Prevent DoS by uninterruptible long regex executions
  * Memory leaks in PL/Perl fixed
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-8.html</changelog>
  <changelog author="max@suse.com" date="1424260800">- Security and bugfix release 9.2.10 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-10.html
- Remove obsolete sle10 patch.
- Improve systemd tempfile handling.</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with later versions.
- Introduce the test subpackage.</changelog>
  <changelog author="jloehel@suse.com" date="1462881600">- Security and bugfix release 9.2.16
  * Fixes: buffer overrun in regular expression processing
  - (CVE-2016-0773) (bnc#966436)
  * Fixes finally: Abnormal termination in PostgreSQL 8.2.5
  - (CVE-2007-4769) (bsc#329282)
  * Fixes: postgresql: privilege escalation issue for users
    of PL/Java
  - (CVE-2016-0766) (bnc#966435)
  * Fixes: Memory leak in crypt() function
  - (CVE-2015-5288) (bnc#949669)
  * Fixes: Avoid possible crash when client disconnects just
    before the authentication timeout expires
  - (CVE-2015-3165) (bnc#931972)
  * Fixes: In contrib/pgcrypto, uniformly report decryption
    failures as "Wrong key or corrupt data
  - (CVE-2015-3167) (bnc#931974)
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-16.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-15.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-14.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-13.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-12.html
    http://www.postgresql.org/docs/9.2/static/release-9-2-11.html</changelog>
  <changelog author="jloehel@suse.com" date="1463745600">- Security and bugfix release 9.2.17
  * Fixes: pgsql conflicts with openssl extension.
    See bug #12799 and https://bugs.php.net/bug.php?id=68276
  * Fix possible read past end of string in to_timestamp().
  * Update time zone data files to tzdata release 2016d.
  * Fix mishandling of equivalence-class tests in parameterized plans.
  * For other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.2/static/release-9-2-17.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.2.18:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-18.html</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.2.19:
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * Suppress printing of zeroes for unmeasured times in EXPLAIN
  * Fix timeout length when VACUUM is waiting for exclusive table
    lock so that it can truncate the table
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.2/static/release-9-2-19.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- Update to version 9.2.20:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.2/static/release-9-2-20.html</changelog>
</package>
<package pkgid="43e8ad404be235ed60afd78770bfeb1b4c9e3b0e1bdf5e779878243999f14e09" name="postgresql93" arch="src">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="03671dc4708b99d23ee409b31383a593c4238ba5b4fa7b49482feacdb68ea355" name="postgresql93" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="b514996427534ad9957baef24d33b653600aea2019aa1c274d9aff7269f82348" name="postgresql93-address_standardizer" arch="src">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="4fe3660a82be0e7d177baef52ac4fd32377729cd53f2f57f09aef4dd057bf0c0" name="postgresql93-address_standardizer" arch="x86_64">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="628281b21f6091bd8397bbb5482ff2bfcc361862dcf4b09033074409799c7a35" name="postgresql93-address_standardizer-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="3b983a741c29bed601e3f065bd3e89ebccf116e5bdad1476bf67540638ae14b9" name="postgresql93-address_standardizer-debugsource" arch="x86_64">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="ab8855b4e4a9128dd8ad5598d175dba5d3e68d0da0e85831eeaca05bd9f83d3b" name="postgresql93-contrib" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="0112c506c455e1587e378e6f5b548fc27b3aabe01556d6785b52c5adfe1e2a89" name="postgresql93-contrib-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="dab839607dc20c75e7e6453753437f6939ca380b881c9ba647dace5404775b12" name="postgresql93-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="c417c9eb3a41c5b3d388a1683ddf4f2d68aef14acd3d4b8b0757548a631c28b3" name="postgresql93-debugsource" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="67ed103047ed171e7d20fdfa70d29aa61d8335169f5cc01cc96ffd9436db61d0" name="postgresql93-devel" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="f3abd5961ca1c7ede41eb4fad8bd14b08180fa5f250deff9ce744faf14631dfe" name="postgresql93-devel-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="59689a3e7f0b8e3ba86687cae7de1c862baf162811a39ad1810d5bf0cee2e66d" name="postgresql93-docs" arch="noarch">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="44a3aa6f1b8203aa8a8ebb7c7c13a9c139401a64fa26c518a17947af015f23cc" name="postgresql93-ip4r" arch="src">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="926971541e9a90745d28eb7cf2a91d0e9c17a1963523fb19ba0d00b68ecc0a0f" name="postgresql93-ip4r" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="4eec8bae4fc4bb0686bac0debf270d86db6317a972fd57de907d73dfbc11dd0a" name="postgresql93-ip4r-debuginfo" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="b4fff42c4c2d63de378685ec7905a5900a71e53cc0fdcbb7ac7008b8fccf31c4" name="postgresql93-ip4r-debugsource" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="da9b5bc6453c4fbb43cbbe81fbf8e9e03d6aff7d2da1a72b122ff8081fb37b4a" name="postgresql93-libs" arch="src">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="faed8780ac503a677c4f56c823fd7097349130fa460e483ca65baa58bc541e26" name="postgresql93-libs-debugsource" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="4478b126044f912e35f980f7d99d2934b33ddef2a7365d8f5ae2268da0408dd5" name="postgresql93-orafce" arch="src">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.1-1" date="1186747200">- Update to 2.1.1
- Spec file cleanup</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-1" date="1200312000">- Update to 2.1.3</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-2" date="1200830400">- Spec file fixes, per bz review #251805</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.4-1" date="1219233600">- Update to 2.1.4</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="e2653113e7c2c9398c37e5891c56d94d1e8dd22688af551586d196710e52eea7" name="postgresql93-orafce" arch="x86_64">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="3f153d4b99a4bc24216675ac85ecbd8b0dd09d6bb07ac5d39c8930e9114e8a3a" name="postgresql93-orafce-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.1-1" date="1186747200">- Update to 2.1.1
- Spec file cleanup</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-1" date="1200312000">- Update to 2.1.3</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-2" date="1200830400">- Spec file fixes, per bz review #251805</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.4-1" date="1219233600">- Update to 2.1.4</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="eeab62a6706a11635851b8dff0a7f16bfe3fe585101e56164ae3b8d842c72e56" name="postgresql93-orafce-debugsource" arch="x86_64">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="d8a5e79ab36dea41c8a9315038ff31c33993b9e9a5a2f58e55489340279d6499" name="postgresql93-pgaudit" arch="src">
  <version epoch="0" ver="1.0.0" rel="4.2"/>
  <changelog author="darin.perusich@ctg.com" date="1412596800">- Initial packaging of pgaudit</changelog>
  <changelog author="darin@darins.net" date="1412683200">- fixed %files path for SLES</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to git HEAD: (adds HEAD.patch)
  - 9bdc2e8 Use bms_{copy,first_member,free} on
    rte-&gt;{selected,modified}Cols
  - 869f4e7 Take column-level privileges into account too
  - 715b653 If audit has been granted permissions, we log the event
  - 7d9313c Make should_be_logged() authoritative by itself
  - 58aa1f4 Describe the current behaviour more precisely
  - 43f9baf If no roles are given, all roles are audited
  - c0b4e6d Add pgaudit.roles setting
  - fe5219f Rename T_AlterTableSpaceMoveStmt to
    T_AlterTableMoveAllStmt following 3c4cf08
  - 98eb0ed We don't need the [] wrapper
  - ab43873 Remove GUC source checking altogether
  - 7782701 Fixes for META.json</changelog>
</package>
<package pkgid="ca7c2842a488e247aa9069de682750f4c97bf01bb6201d54a11f8b903edd907b" name="postgresql93-pgaudit" arch="x86_64">
  <version epoch="0" ver="1.0.0" rel="4.2"/>
  <changelog author="darin.perusich@ctg.com" date="1412596800">- Initial packaging of pgaudit</changelog>
  <changelog author="darin@darins.net" date="1412683200">- fixed %files path for SLES</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to git HEAD: (adds HEAD.patch)
  - 9bdc2e8 Use bms_{copy,first_member,free} on
    rte-&gt;{selected,modified}Cols
  - 869f4e7 Take column-level privileges into account too
  - 715b653 If audit has been granted permissions, we log the event
  - 7d9313c Make should_be_logged() authoritative by itself
  - 58aa1f4 Describe the current behaviour more precisely
  - 43f9baf If no roles are given, all roles are audited
  - c0b4e6d Add pgaudit.roles setting
  - fe5219f Rename T_AlterTableSpaceMoveStmt to
    T_AlterTableMoveAllStmt following 3c4cf08
  - 98eb0ed We don't need the [] wrapper
  - ab43873 Remove GUC source checking altogether
  - 7782701 Fixes for META.json</changelog>
</package>
<package pkgid="399b8a1ec5fb2fed79700d668b9b2bfb0c2e58eb63eaf7f24d64e3377dfe01d7" name="postgresql93-pgaudit-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.0.0" rel="4.2"/>
  <changelog author="darin.perusich@ctg.com" date="1412596800">- Initial packaging of pgaudit</changelog>
  <changelog author="darin@darins.net" date="1412683200">- fixed %files path for SLES</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to git HEAD: (adds HEAD.patch)
  - 9bdc2e8 Use bms_{copy,first_member,free} on
    rte-&gt;{selected,modified}Cols
  - 869f4e7 Take column-level privileges into account too
  - 715b653 If audit has been granted permissions, we log the event
  - 7d9313c Make should_be_logged() authoritative by itself
  - 58aa1f4 Describe the current behaviour more precisely
  - 43f9baf If no roles are given, all roles are audited
  - c0b4e6d Add pgaudit.roles setting
  - fe5219f Rename T_AlterTableSpaceMoveStmt to
    T_AlterTableMoveAllStmt following 3c4cf08
  - 98eb0ed We don't need the [] wrapper
  - ab43873 Remove GUC source checking altogether
  - 7782701 Fixes for META.json</changelog>
</package>
<package pkgid="c37432aa4b40b073ea4ac3d6519020f6c24e92528cffa358636b634e231ac83b" name="postgresql93-pgaudit-debugsource" arch="x86_64">
  <version epoch="0" ver="1.0.0" rel="4.2"/>
  <changelog author="darin.perusich@ctg.com" date="1412596800">- Initial packaging of pgaudit</changelog>
  <changelog author="darin@darins.net" date="1412683200">- fixed %files path for SLES</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to git HEAD: (adds HEAD.patch)
  - 9bdc2e8 Use bms_{copy,first_member,free} on
    rte-&gt;{selected,modified}Cols
  - 869f4e7 Take column-level privileges into account too
  - 715b653 If audit has been granted permissions, we log the event
  - 7d9313c Make should_be_logged() authoritative by itself
  - 58aa1f4 Describe the current behaviour more precisely
  - 43f9baf If no roles are given, all roles are audited
  - c0b4e6d Add pgaudit.roles setting
  - fe5219f Rename T_AlterTableSpaceMoveStmt to
    T_AlterTableMoveAllStmt following 3c4cf08
  - 98eb0ed We don't need the [] wrapper
  - ab43873 Remove GUC source checking altogether
  - 7782701 Fixes for META.json</changelog>
</package>
<package pkgid="094f0ad9d807e53176b2314f73a8b1ff7e53e6c5b51b0d0ee1845fe35ba04bcf" name="postgresql93-pgpool-II" arch="src">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="40711a2c713379bd580d7289d8ddfeabf4fdd7bbfd33c3c07421b2e29b9884e4" name="postgresql93-pgpool-II" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="554325752287a36a5496602ab2428d0b4cb9982f7bdb277bd81df5b7b4a70e28" name="postgresql93-pgpool-II-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="50de8053204dddc0491011b32fbcdb0569c121cbfcfff83aa21b2ac627a816cd" name="postgresql93-pgpool-II-debugsource" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="696d4c1d9d2afd9c4771c7859ec8e0b800533e0ef5694a321a5d89c5d0b0f4f3" name="postgresql93-plperl" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="4c73ffcebef3a74e2d94aade1682365ac3eb6e7f4812a4e1d52c6acf8f1ada60" name="postgresql93-plperl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="63418f86a44bd28dae45cdc54d55eca5be0a459bb3d9a99b66cfb8454a1f7f12" name="postgresql93-plpython" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="87b36f21037f04d4322020ca72baa554ab71f21dcaebfc3440fb47637460e2e3" name="postgresql93-plpython-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="21f4a66408d17e22c8e7413c5fa2ffc46b545f53b923868f81648471dddd9ed0" name="postgresql93-plr" arch="src">
  <version epoch="0" ver="8.3.0.17" rel="11.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="7f24275ec5244f1f4193f00eb7d33ed2deb73e31fd65f680e96bb5df1c3ffe74" name="postgresql93-plr" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="11.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="b3ff29c1db56cf6eb26b3dd4d47cd53247723de1eb3a842b957aabf6d3700bda" name="postgresql93-plr-debuginfo" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="11.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="78c9023d8ada098715f427b81307a015b9b09fce5addb3bd1b6405d4155e9799" name="postgresql93-plr-debugsource" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="11.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="e44521b19255f6ea494ee165ac30246b772f1636dc3a933341655a24c3cfd333" name="postgresql93-plr-doc" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="11.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="f8f1f99491ece4b096469f183befba8f65dcefebc714f80b36785d44dca59f0d" name="postgresql93-pltcl" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="b82be9a916a3a8c1a6f27763b56f191e9069b67575d81f8be4be214eb7c19632" name="postgresql93-pltcl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="cae37f8d54f66fbe13c45d362ad3665e9d0c2f18d3c503ef5d8c8420f37d7771" name="postgresql93-repmgr" arch="src">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="a67a3b6d9d621a0acd471ac8734cb2783809529779558115c97c116edbef4f7a" name="postgresql93-repmgr" arch="x86_64">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="f2e9d7145f745f7eb5560bee5329bb9f49ab65ade44146df301287d2c78cc6b5" name="postgresql93-repmgr-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="fae157cd46db695eaad93af54908d19a56d3702c0203f4c4aec33b35e9a19ef8" name="postgresql93-repmgr-debugsource" arch="x86_64">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="3980248b1ca87222730a0ff098c6283a2041833461f29e55e86593d79fe7bbbc" name="postgresql93-server" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="201de3fbbfa6bc0a7705f88dd634422d3837f212fcf393d6aa1e4089dd09f79e" name="postgresql93-server-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="55449b6aeaef0374233278bd00449b15f21a5b404595e1fb915ad263b768a3f0" name="postgresql93-test" arch="x86_64">
  <version epoch="0" ver="9.3.17" rel="63.1"/>
  <changelog author="max@suse.com" date="1406289600">- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch
- Rediff patches.</changelog>
  <changelog author="ro@suse.de" date="1406289601">- add BuildIgnore systemd-mini to fix build</changelog>
  <changelog author="darin@darins.net" date="1406635200">- fix systemd unresolvable for SLE_11
  http://en.opensuse.org/openSUSE:Systemd_packaging_guidelines</changelog>
  <changelog author="coolo@suse.com" date="1406808000">- postgresql93-libs doesn't require systemd - avoid cycles</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with version 9.4 and improve the building of
  libs and devel.</changelog>
  <changelog author="max@suse.com" date="1424433600">- Security and bugfix release 9.3.6 (bnc#916953):
  * Fix buffer overruns in to_char() (CVE-2015-0241).
  * Fix buffer overrun in replacement *printf() functions
    (CVE-2015-0242).
  * Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243).
  * Fix possible loss of frontend/backend protocol synchronization
    after an error (CVE-2015-0244).
  * Fix information leak via constraint-violation error messages
    (CVE-2014-8161).
  * For the other bug fixes, see the release notes:
    http://www.postgresql.org/docs/9.3/static/release-9-3-6.html</changelog>
  <changelog author="max@suse.com" date="1432296000">- Security and bugfix release 9.3.7:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of the
  * printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly report
    decryption failures as "Wrong key or corrupt data"
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-7.html</changelog>
  <changelog author="max@suse.com" date="1433332800">- Bugfix release 9.3.8:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF
    property, if set.
  * Allow libpq to use TLS protocol versions beyond v1.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-8.html</changelog>
  <changelog author="max@suse.com" date="1440072000">- Merge openSUSE and SLE12 packages (bsc#941886).
- Merge .changes, remove duplicate entries and fix syntax
  violations at the very bottom.
- postgresql-sle10-timestamptz.patch is obsolete.
- remove baselibs.conf, because we don't build the libarries any
  longer.
- Bugfix release 9.3.9:
  * Fix possible failure to recover from an inconsistent database
    state. See full release notes for details.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-9.html</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.3.10:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-3-10.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals.
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.3.11:
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notse, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-11.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.3.12:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.3/static/release-9-3-12.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release 9.3.13
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-3-13.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.3.14:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-14.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.3.15:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * Fix EXPLAIN to emit valid XML when track_io_timing is on
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.3/static/release-9-3-15.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.3.16:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.3/static/release-9-3-16.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.3.16-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.3.17:
  * https://www.postgresql.org/docs/9.3/static/release-9-3-16.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.3.16-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="0c8b132c186762ace8596417b94be973e6117cb3984dabbd56cf0258fa4d1c4f" name="postgresql94" arch="src">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="ed1ef058ace05c2d841269a45b9cf0c267348615e7773cec84f905ca19d1298e" name="postgresql94" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="89a2d08860c26e0b2118d6bc4dd5cda788b4342829065f20bab533ddaf4db771" name="postgresql94-address_standardizer" arch="src">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="aac2e4318edfe19e7e27113e8e8f81dadef0dc14db3bd1b92c91dae1baeb7d09" name="postgresql94-address_standardizer" arch="x86_64">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="bf8113a9acbafe6588107ef5b273982e54aa10e8d5d46e712edf8f9000194911" name="postgresql94-address_standardizer-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="1a58e1bb1307ed172acd1ce2a12b623b0dc23abf223f6df4890ac60aabc82ea3" name="postgresql94-address_standardizer-debugsource" arch="x86_64">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="cc37f853c11281b82beb5898b6b50cc7f9c91627d41f18934235801df3e67ee2" name="postgresql94-contrib" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="d0e2c2559cf228a83605c37188e17e555f97a385a6e98b4261be22030f19756d" name="postgresql94-contrib-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="26aa1077a3fa0912c4c8ebef33989c50f9246bfb6b621cde035b24ffa5ffb7f7" name="postgresql94-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="0a1eb0a5f22352974d5b7d745adc82fcdfd28d51b6860257a103e8f99076ce08" name="postgresql94-debugsource" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="d7dd693147913a338e60e6eb378dcb49067110e6428ef523692120bf01871da9" name="postgresql94-devel" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="dcb12e3fc5f8cfe2ee42b1ad9b249acba901c081ec3a895dfa5bdf114db4726f" name="postgresql94-devel-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="a9cb04703df3b6dcfde68a91aace986909aec6ad9900474dee299f422fa557ea" name="postgresql94-docs" arch="noarch">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="e980a66c34e5191b2f71943fd084dc7e5f222486daa3111b4b6a429b902015a2" name="postgresql94-ip4r" arch="src">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="4924e9838282bcbe9ca4388109f948e1d9c61c8de2c0116896b203865bddadf7" name="postgresql94-ip4r" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="c446651068e7117c287aedbf185320219132325fa7d83a3872dfe0171f0442f2" name="postgresql94-ip4r-debuginfo" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="7d17cc36f333975126b54c9c6b547a16e7e024661ad0c89f44f08a26474282e0" name="postgresql94-ip4r-debugsource" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="ede07c501b3f1b319888d420ca4e5029403b5d72b153ed96f5ad9e9cd38e2dc7" name="postgresql94-libs" arch="src">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="e80067bb0fc46aeb454605ee544a3a253b4e6e3b5e2ad8e8b6c0b5382774f4a9" name="postgresql94-libs-debugsource" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="5eb24721cda623875194357a91a740c4c19bd6918a0f00e7b664844c1e6af9bc" name="postgresql94-orafce" arch="src">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.1-1" date="1186747200">- Update to 2.1.1
- Spec file cleanup</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-1" date="1200312000">- Update to 2.1.3</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-2" date="1200830400">- Spec file fixes, per bz review #251805</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.4-1" date="1219233600">- Update to 2.1.4</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="bf9a46cea0df5f8ae737b2249053576b2aa84a54c3580a31d9e96866aa7c481a" name="postgresql94-orafce" arch="x86_64">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="fd60fccd3a1e1e06733b380ba7525da17487ca02de6a24a3dc4cd01ae48a1c4b" name="postgresql94-orafce-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.1-1" date="1186747200">- Update to 2.1.1
- Spec file cleanup</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-1" date="1200312000">- Update to 2.1.3</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.3-2" date="1200830400">- Spec file fixes, per bz review #251805</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 2.1.4-1" date="1219233600">- Update to 2.1.4</changelog>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="42fbff20fce9d3f45c3cf1b604125b0b16392bfed25e9efd6a785f964d58a8d1" name="postgresql94-orafce-debugsource" arch="x86_64">
  <version epoch="0" ver="3.0.9" rel="13.3"/>
  <changelog author="Devrim GUNDUZ &lt;devrim@commandprompt.com&gt; - 3.0.1-1" date="1254484800">- Update to 3.0.1
- Remove patch0, it is in upstream now.
- Apply some 3.0 fixes to spec.</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-2" date="1271678400">- Make some cleanup as described in #251805
- Clean %%files section
- Rename the package back to postgresql-orafce to be consistent with other extensions</changelog>
  <changelog author="Jean-Francois Saucier &lt;jfsaucier@infoglobe.ca&gt; - 3.0.1-3" date="1272456000">- Rename back the package to orafce after discussion on devel list</changelog>
  <changelog author="Darin Perusich &lt;darin@darins.net&gt;" date="1302868800">- Ported to OpenSuSE
- Update to 3.0.3</changelog>
  <changelog author="darin@darins.net" date="1323777600">- moved %changelog to .changes file</changelog>
  <changelog author="darin@darins.net" date="1323777601">- updated package to 3.0.4</changelog>
  <changelog author="darin@darins.net" date="1323777602">- added FLEX=/usr/bin/flex to make statement in %build.
  See http://pgfoundry.org/forum/forum.php?set=custom&amp;forum_id=410&amp;style=nested&amp;max_rows=25&amp;submit=Change+View</changelog>
  <changelog author="darin@darins.net" date="1323777603">- Fixed non-standard Group</changelog>
  <changelog author="darin@darins.net" date="1351166400">- updated to orafce-HEAD-36ccc5b from git repository which supports
  postgresql 9.2. As there's no official release i'm calling it 5a
- created .specs to support multiple versions of PG
- removed/renamed orafce.spec</changelog>
  <changelog author="darin@darins.net" date="1351252800">- added pre_checkin.sh to generate .spec and .changes</changelog>
  <changelog author="darin@darins.net" date="1351771200">- updated name in template
- set proper install location</changelog>
  <changelog author="darin@darins.net" date="1355745600">- renamed orafce.spec to orafce.spec.in</changelog>
  <changelog author="darin@darins.net" date="1375963200">- patch for compilation error with Bison &gt;=2.6
  See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710633</changelog>
  <changelog author="darin@darins.net" date="1381320000">- updated to verion 3.0.6
- generate specs for PG 9.3</changelog>
  <changelog author="darin@darins.net" date="1381752000">- rename README.orafunc to README.asciidoc</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 3.0.9
  * PostgreSQL 9.4 compilation
  * new datatype and related functions: oracle.date
  * new varchar2, nvarchar2 types and related functions
    (Amit Langote)
  * oracle.substr emulate better Oracle substr function behave
    (Vinayak Pokale)
  * fix few internal issues that breaks a PGXN tests (Pavel Stehule)</changelog>
</package>
<package pkgid="a773f44283872ae8f655ff8f89532fdf57e0b08be48139075b837afc7be73c6d" name="postgresql94-pgaudit" arch="src">
  <version epoch="0" ver="1.0.0" rel="4.2"/>
  <changelog author="darin.perusich@ctg.com" date="1412596800">- Initial packaging of pgaudit</changelog>
  <changelog author="darin@darins.net" date="1412683200">- fixed %files path for SLES</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to git HEAD: (adds HEAD.patch)
  - 9bdc2e8 Use bms_{copy,first_member,free} on
    rte-&gt;{selected,modified}Cols
  - 869f4e7 Take column-level privileges into account too
  - 715b653 If audit has been granted permissions, we log the event
  - 7d9313c Make should_be_logged() authoritative by itself
  - 58aa1f4 Describe the current behaviour more precisely
  - 43f9baf If no roles are given, all roles are audited
  - c0b4e6d Add pgaudit.roles setting
  - fe5219f Rename T_AlterTableSpaceMoveStmt to
    T_AlterTableMoveAllStmt following 3c4cf08
  - 98eb0ed We don't need the [] wrapper
  - ab43873 Remove GUC source checking altogether
  - 7782701 Fixes for META.json</changelog>
</package>
<package pkgid="63b417ccb8c9190e0d902f2ead4e8be6b73a29c33a6d5b3e8c43f45c58ba831a" name="postgresql94-pgaudit" arch="x86_64">
  <version epoch="0" ver="1.0.0" rel="4.2"/>
  <changelog author="darin.perusich@ctg.com" date="1412596800">- Initial packaging of pgaudit</changelog>
  <changelog author="darin@darins.net" date="1412683200">- fixed %files path for SLES</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to git HEAD: (adds HEAD.patch)
  - 9bdc2e8 Use bms_{copy,first_member,free} on
    rte-&gt;{selected,modified}Cols
  - 869f4e7 Take column-level privileges into account too
  - 715b653 If audit has been granted permissions, we log the event
  - 7d9313c Make should_be_logged() authoritative by itself
  - 58aa1f4 Describe the current behaviour more precisely
  - 43f9baf If no roles are given, all roles are audited
  - c0b4e6d Add pgaudit.roles setting
  - fe5219f Rename T_AlterTableSpaceMoveStmt to
    T_AlterTableMoveAllStmt following 3c4cf08
  - 98eb0ed We don't need the [] wrapper
  - ab43873 Remove GUC source checking altogether
  - 7782701 Fixes for META.json</changelog>
</package>
<package pkgid="7d584d18452b9952aaee54c657de0a3f94c45ffb49ffb17bc9f0dcc50c462c77" name="postgresql94-pgaudit-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.0.0" rel="4.2"/>
  <changelog author="darin.perusich@ctg.com" date="1412596800">- Initial packaging of pgaudit</changelog>
  <changelog author="darin@darins.net" date="1412683200">- fixed %files path for SLES</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to git HEAD: (adds HEAD.patch)
  - 9bdc2e8 Use bms_{copy,first_member,free} on
    rte-&gt;{selected,modified}Cols
  - 869f4e7 Take column-level privileges into account too
  - 715b653 If audit has been granted permissions, we log the event
  - 7d9313c Make should_be_logged() authoritative by itself
  - 58aa1f4 Describe the current behaviour more precisely
  - 43f9baf If no roles are given, all roles are audited
  - c0b4e6d Add pgaudit.roles setting
  - fe5219f Rename T_AlterTableSpaceMoveStmt to
    T_AlterTableMoveAllStmt following 3c4cf08
  - 98eb0ed We don't need the [] wrapper
  - ab43873 Remove GUC source checking altogether
  - 7782701 Fixes for META.json</changelog>
</package>
<package pkgid="91db6bb5e587bfff84485762673735bfb2f7d4125834e8c1e85ca663adf5e827" name="postgresql94-pgaudit-debugsource" arch="x86_64">
  <version epoch="0" ver="1.0.0" rel="4.2"/>
  <changelog author="darin.perusich@ctg.com" date="1412596800">- Initial packaging of pgaudit</changelog>
  <changelog author="darin@darins.net" date="1412683200">- fixed %files path for SLES</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to git HEAD: (adds HEAD.patch)
  - 9bdc2e8 Use bms_{copy,first_member,free} on
    rte-&gt;{selected,modified}Cols
  - 869f4e7 Take column-level privileges into account too
  - 715b653 If audit has been granted permissions, we log the event
  - 7d9313c Make should_be_logged() authoritative by itself
  - 58aa1f4 Describe the current behaviour more precisely
  - 43f9baf If no roles are given, all roles are audited
  - c0b4e6d Add pgaudit.roles setting
  - fe5219f Rename T_AlterTableSpaceMoveStmt to
    T_AlterTableMoveAllStmt following 3c4cf08
  - 98eb0ed We don't need the [] wrapper
  - ab43873 Remove GUC source checking altogether
  - 7782701 Fixes for META.json</changelog>
</package>
<package pkgid="8657af555cebb4a18734d5af3019be3ae55f6a74b086555d0c0624179dd7f4ca" name="postgresql94-pgpool-II" arch="src">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="8b2a57d1a16704290f0a9d8c532e294cee9304e04af4c1469cc9fb3d0d3a4b9c" name="postgresql94-pgpool-II" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="3d55e0f1d1dc2520a5ee79836299b6c4d32e33676fa5be7430d11b0b9a5e2728" name="postgresql94-pgpool-II-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="01c03f392d72277f7fa0dde786fda072594677f32a1753313a96b6de95057088" name="postgresql94-pgpool-II-debugsource" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="0639e74118037769a0977e0a8b79600a09ec1a9612af0633731dd822d8be9134" name="postgresql94-plperl" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="0b94a03b54591afe72e06d5f273074c1533e0961d09abc9c8734e6cb85c12209" name="postgresql94-plperl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="bbe6de5649c8acaf4dcdd64ec9dc8bfcae4affadf08846259b3e43c028b3fd59" name="postgresql94-plpython" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="dbd2399397ec0b443def20f5165e67ff682895e6d11c70cb23116045d2c288d9" name="postgresql94-plpython-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="cd742032249f936c3a098fa2e4193f8d87dbe4b6cc225ea8570b1f096cb0c2e8" name="postgresql94-plr" arch="src">
  <version epoch="0" ver="8.3.0.17" rel="5.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="4196ec10878ab039c3ba7356dff7c475bb258969aa8587ee88ac971d30b70002" name="postgresql94-plr" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="5.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="3893b28e3663931e9cc4c6827f6652ff489c2a390b816386ad9ec03e9de9a234" name="postgresql94-plr-debuginfo" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="5.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="9c268bdf03e2e54524f6a23a8e3715a752e49bb7d74f5f7e629b20eb1aef1975" name="postgresql94-plr-debugsource" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="5.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="a004e93aeb93d8e8bd0a1281eba2e8d5969cb6a2f1b3c408f280b8d81dde9922" name="postgresql94-plr-doc" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="5.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="9b833edcd132e5e66b2eff5ff1f62ad906a6f2fc2cdd314c28d2ecc4209f2ec8" name="postgresql94-pltcl" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="d78318b5e4e8f29335d7724da50c8eff4b6997fbb265bdb7558304d79886fa17" name="postgresql94-pltcl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="12ef242cc786331ad083134a8a1c2f4cca366515d71b05063a25eb150f4dacab" name="postgresql94-repmgr" arch="src">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="c2dbdcf28d78c92d8d662883b1f70117ac7760be26aa5fe3ac35bc09d29042c2" name="postgresql94-repmgr" arch="x86_64">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="85b16ba6500705d7d9e64b0ac980f86ebb520ff08298656e373176a8a1521e48" name="postgresql94-repmgr-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="55094064c94f524584473d1024f6a321043de18596596e14f6362314e53c6211" name="postgresql94-repmgr-debugsource" arch="x86_64">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="abd6563ea7b03ee5ac44d95d97ff75b582c26670208955c7546c4b0249b555d3" name="postgresql94-server" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="967ac50e0594020ac2d8e410b0d9610106419ff39e1447dd2efd7f9211fb79aa" name="postgresql94-server-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="35c83e811d4f29e3040e58efc9ed1b8099ea5b3d18b7b555607d57fa3be816b5" name="postgresql94-test" arch="x86_64">
  <version epoch="0" ver="9.4.12" rel="21.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notes, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Bugfix release 9.4.7:
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- Bugfix release to 9.4.8
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-4-8.html</changelog>
  <changelog author="max@suse.com" date="1464004800">- The libs are now built in 9.5, so disable them here and remove
  baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.4.9:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Make the inet and cidr data types properly reject IPv6
    addresses with too many colon-separated fields
  * Prevent crash in close_ps() (the point ## lseg operator) for
    NaN input coordinates
  * Fix several one-byte buffer over-reads in to_number()
  * Avoid unsafe intermediate state during expensive paths through
    heap_update()
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-9.html</changelog>
  <changelog author="fweiss@suse.com" date="1473940800">- Added "Requires: timezone" to Server Package (bsc#973660)</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.4.10:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix improper repetition of previous results from hashed
    aggregation in a subquery
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.4/static/release-9-4-10.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.4.11:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.4/static/release-9-4-11.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.4.11-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494331200">- Update to version 9.4.12:
  * https://www.postgresql.org/docs/9.4/static/release-9-4-12.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Move the timezone requirement to the server package as it was
  originally intended.
- Sync spec file with postgresql96.
- Merge Factory and SLE-12.</changelog>
</package>
<package pkgid="a2002b85b7d66fe6e9fde13e79dad67109a3163f8492131cf7ff87d717ecc7f5" name="postgresql95" arch="src">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="c4721df8dfdbda6fe8344ec37e385c0dc95daffd7e221b90d61c273d0d06b660" name="postgresql95" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="1bf3989c65d118cea85215e3b81a3d7e3193dbf690b4bbff71d6942f9a381f6a" name="postgresql95-address_standardizer" arch="src">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="6d07dcfd3577e1e5b86b9f0c328f9ab936ff1b159cee8865c993ad179fb97126" name="postgresql95-address_standardizer" arch="x86_64">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="b85f2e6b7762eecaebb1918d98094b5d96631dcfa933f5b30d6f8f84c58fc31d" name="postgresql95-address_standardizer-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="9b4ae10e1da64c73aa90d0bc92b7ec1a06d0c0dfde44846683952f96af3778cb" name="postgresql95-address_standardizer-debugsource" arch="x86_64">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="a5323db210edc3aab6ed3dc60672991f327e3be0959161dc7f288926dfd2d010" name="postgresql95-contrib" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="abb37b8fe1ba6e3c673a8dcb130adee5dd1a0ed4da7e688ea9d639e0a2638cf9" name="postgresql95-contrib-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="e219ef78859099b8bada4c1c63cbd38271202e0624842e2c3e4b593570b8e35b" name="postgresql95-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="617444465271795be09744e5b3dc7e584be6b2c8c436a19db7ab123aedbc5732" name="postgresql95-debugsource" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="8448a2c225a4cae7385ab15849417024d352087439908c52967c99b6a0e45df2" name="postgresql95-devel" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="d065fd0c719fe2e7de64f3763ba1dc1d2a0a51f554859809235f6eefe64f9e14" name="postgresql95-devel-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="a6d2e7878b87453a39e98cf10c728b9cff1ed717a1d555cb2e93f7e858133b92" name="postgresql95-docs" arch="noarch">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="b5590065092747bb71cc4c1e83ccdf23bc41121837af4d2475081f4ebca09fe3" name="postgresql95-ip4r" arch="src">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="5e33283fb51450790577d6a1cfe8078090ceae08bd9c826d61797848dc481772" name="postgresql95-ip4r" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="fb67f62ba27d6a9432886a4c31446b3de28c403a9b8de565140078421f67f776" name="postgresql95-ip4r-debuginfo" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="a3cd784757ae26abc7e0ea776008305ab487d00fb5a1d9be754b66e9fec1baff" name="postgresql95-ip4r-debugsource" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="89aa1e9a55884f8ba902bcce744b6132d721c0d50c2dfac227286eb15b26699a" name="postgresql95-libs" arch="src">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="e6cea0d95ed9fdb6866094f5c93a581bd20be90f3d5ceb8657e99641ddf4e5b5" name="postgresql95-libs-debugsource" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="71fa2208086bcf921dbf35665e26603f58959fd34cfa6d8ad30bee93189f6d3a" name="postgresql95-pgpool-II" arch="src">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="37bf4528fcdcbcfbb8b1a5eed00946caa6a76c37ad50735647b66c18ac3b60ee" name="postgresql95-pgpool-II" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="06183a253c165751991a324b3a5f8040f3a940f24c979a6608003d731f7034fb" name="postgresql95-pgpool-II-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="436116c79cde8ff9ef46f69d7f971b606e6942bb72c55558df64c33b0e271087" name="postgresql95-pgpool-II-debugsource" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="6a65f09773529abf3747055f4ab2e989817b7bb98bcb2d498d4aaee613456cab" name="postgresql95-plperl" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="d427983ed41c1de87aa0755a8fb284f948975da0742789284a646865ee900d60" name="postgresql95-plperl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="e5e0ff15dcdf0999bfffb2f81dfe088a1851462caac15a1614a6537f514a06a1" name="postgresql95-plpython" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="68d747deacb44461cf031b90ad71c455391703ad3977740808d07a420b6b2a24" name="postgresql95-plpython-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="a357c3df36fa3a4bab3760339e63252c33defc6f54c0b856db3ddb9c2462151c" name="postgresql95-plr" arch="src">
  <version epoch="0" ver="8.3.0.17" rel="4.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="a2d6fbac978307f3c99763a1af7e62b390f1a743216abe73f9591fc12a077283" name="postgresql95-plr" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="4.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="21b6d816df4d0466cf09918064c08dab7a9d01392d99de43e07cf4d6be50345d" name="postgresql95-plr-debuginfo" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="4.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="8e90313a5dee86b7496525014c61910d227e8a5a2353a4d3c4bdf0c816eec6d2" name="postgresql95-plr-debugsource" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="4.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="2fd69de2768b4656f5f6eeb79f9f3c01b4c19668cbdd3a0abfe20aca74c11dd0" name="postgresql95-plr-doc" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="4.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
</package>
<package pkgid="15aaf8e325fe988059bce11ddc256c1745a3865e4db61b9f92686dfc92a2d32b" name="postgresql95-pltcl" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="c2cf97c79c764b4680909e7be4ee16c28dd6da2ac4a3d025d524c0abc106d972" name="postgresql95-pltcl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="14be66f771a9b2412e54302d996a871204f6f29f3f3261b1e32eb35d6091c1d5" name="postgresql95-repmgr" arch="src">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="d7d3565254386daebf758a10f4811726148bfcbd215258d7f082889a08af7d84" name="postgresql95-repmgr" arch="x86_64">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="6fe8774cbce622b03e07cdefeedc8e1abc11692c9d3e14ab555c1b1c6ecd30bc" name="postgresql95-repmgr-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="ed2179d11450e5e3f734efad0542d62035781cdbfdfacbee0a56d82ad9a97a7e" name="postgresql95-repmgr-debugsource" arch="x86_64">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="d9a8ce786d76f97d724a75c613982353e30587abfc488b29f1abcec0bf4778ab" name="postgresql95-server" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="9b7b40cd4d456e155c5569ad25ec0fa81490b901a39788c5bca03bf6e4a71224" name="postgresql95-server-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="7cc41ec98641d15e8ffc25a9ce5897be968c8245babe94334cf80d73cab05fdd" name="postgresql95-test" arch="x86_64">
  <version epoch="0" ver="9.5.7" rel="14.1"/>
  <changelog author="darin@darins.net" date="1423224000">- Update to 9.4.1
  * Fix buffer overruns in to_char()
  * Fix buffer overrun in replacement *printf() functions
  * Fix buffer overruns in contrib/pgcrypto
  * Fix possible loss of frontend/backend protocol synchronization
  after an error
  * Fix information leak via constraint-violation error messages
  * Lock down regression testing's temporary installations on Windows
  * Cope with the Windows locale named "Norwegian (Bokmål)"
  * Fix use-of-already-freed-memory problem in EvalPlanQual processing
  * Avoid possible deadlock while trying to acquire tuple locks in
  EvalPlanQual processing
  * Improve performance of EXPLAIN with large range tables
  * Fix jsonb Unicode escape processing, and in consequence disallow
  \u0000
  * Fix namespace handling in xpath()
  * Fix assorted oversights in range-operator selectivity estimation
  * Revert unintended reduction in maximum size of a GIN index item
  * Fix query-duration memory leak during repeated GIN index rescans
  * Fix possible crash when using nonzero gin_fuzzy_search_limit
  * Assorted fixes for logical decoding
  * Fix incorrect replay of WAL parameter change records that report
  changes in the wal_log_hints setting
  * Change "pgstat wait timeout" warning message to be LOG level, and
  rephrase it to be more understandable
  * Warn if OS X's setlocale() starts an unwanted extra thread inside
  the postmaster
  * Fix libpq's behavior when /etc/passwd isn't readable
  * Improve consistency of parsing of psql's special variables
  * Fix pg_dump to handle comments on event triggers without failing
  * Allow parallel pg_dump to use --serializable-deferrable
  * Prevent WAL files created by pg_basebackup -x/-X from being
  archived again when the standby is promoted
  * Handle unexpected query results, especially NULLs, safely in
  contrib/tablefunc's connectby()
  * Numerous cleanups of warnings from Coverity static code analyzer
  * Allow CFLAGS from configure's environment to override
  automatically-supplied CFLAGS
  * Make pg_regress remove any temporary installation it created
  upon successful exit
  * Add CST (China Standard Time) to our lists of timezone abbreviations
  * Update time zone data files to tzdata release 2015a for DST law
  changes in Chile and Mexico, plus historical changes in Iceland.</changelog>
  <changelog author="mrueckert@suse.de" date="1423742400">- majorversion should only be 9.4</changelog>
  <changelog author="max@suse.com" date="1424260800">- Switch over to 9.4 by building the libs package and disable it
  on 9.3.
- Remove obsolete patches:
  * postgresql-sle10-timestamptz.patch
  * postgresql-plperl.patch</changelog>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463659200">- update to 9.5.3
  This update fixes several problems which caused downtime for
  users, including:
  - Clearing the OpenSSL error queue before OpenSSL calls,
    preventing errors in SSL connections, particularly when using
    the Python, Ruby or PHP OpenSSL wrappers
  - Fixed the "failed to build N-way joins" planner error
  - Fixed incorrect handling of equivalence in multilevel nestloop
    query plans, which could emit rows which didn't match the WHERE
    clause.
  - Prevented two memory leaks with using GIN indexes, including a
    potential index corruption risk.
  The release also includes many other bug fixes for reported
  issues, many of which affect all supported versions:
  - Fix corner-case parser failures occurring when
    operator_precedence_warning is turned on
  - Prevent possible misbehavior of TH, th, and Y,YYY format codes
    in to_timestamp()
  - Correct dumping of VIEWs and RULEs which use ANY (array) in a
    subselect
  - Disallow newlines in ALTER SYSTEM parameter values
  - Avoid possible misbehavior after failing to remove a tablespace
    symlink
  - Fix crash in logical decoding on alignment-picky platforms
  - Avoid repeated requests for feedback from receiver while
    shutting down walsender
  - Multiple fixes for pg_upgrade
  - Support building with Visual Studio 2015
  - This update also contains tzdata release 2016d, with updates
    for Russia, Venezuela, Kirov, and Tomsk.
  http://www.postgresql.org/docs/current/static/release-9-5-3.html</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to version 9.5.4:
  * Fix possible mis-evaluation of nested CASE-WHEN expressions
    (CVE-2016-5423, bsc#993454)
  * Fix client programs' handling of special characters in database
    and role names (CVE-2016-5424, bsc#993453)
  * Fix corner-case misbehaviors for IS NULL/IS NOT NULL applied
    to nested composite values
  * Fix "unrecognized node type" error for INSERT ... ON CONFLICT
    within a recursive CTE (a WITH item)
  * Fix INSERT ... ON CONFLICT to successfully match index
    expressions or index predicates that are simplified during the
    planner's expression preprocessing phase
  * Correctly handle violations of exclusion constraints that apply
    to the target table of an INSERT ... ON CONFLICT command, but
    are not one of the selected arbiter indexes
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-4.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.
- Drop baselibs.conf.</changelog>
  <changelog author="fweiss@suse.com" date="1481198400">- Update to version 9.5.5:
  * Fix WAL-logging of truncation of relation free space maps and
    visibility maps
  * Fix incorrect creation of GIN index WAL records on big-endian
    machines
  * Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have
    been updated by a subsequently-aborted transaction
  * Fix EvalPlanQual rechecks involving CTE scans
  * Fix deletion of speculatively inserted TOAST tuples when
    backing out of INSERT ... ON CONFLICT
  * For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-5.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- Update to version 9.5.6:
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  - For the other bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.5/static/release-9-5-6.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a bsc#1029547
  postgresql-9.5.6-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.5.7:
  * https://www.postgresql.org/docs/9.4/static/release-9-5-7.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.4.11-fix-timezone-tests.patch
- Add "Requires: timezone" to Server Package (bsc#973660).
- Sync spec file with postgresql96.</changelog>
</package>
<package pkgid="37d72db8e609070ead5948464a4a3db36e0589edca151d5f0fdc888c734e55d0" name="postgresql96" arch="src">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="bf747a72ecf0a19fa7faa19849e011c58dda06f8622944297e260a5e24f7ad5d" name="postgresql96" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="f3155e9101fc6ed53645a2799d838697e8106700951167969c202ed559551d77" name="postgresql96-address_standardizer" arch="src">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="e1cecd6df6647e4399c68ebde00c2eb443aae806fa269adf72ae955add3bdc6a" name="postgresql96-address_standardizer" arch="x86_64">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="1ffa99c3727732362294e26757c0210cf08c859ace7c81d18d24ed1e7506e32d" name="postgresql96-address_standardizer-debuginfo" arch="x86_64">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="d9647a747c67dd19e733fc5fa97a5a9119d501c70e2dd35c43b27ef6d6b54e9d" name="postgresql96-address_standardizer-debugsource" arch="x86_64">
  <version epoch="0" ver="1.0" rel="3.1"/>
  <changelog author="darin@darins.net" date="1427112000">- initial packaging</changelog>
  <changelog author="darin@darins.net" date="1427112001">- fix name in %setup</changelog>
</package>
<package pkgid="0c846a105c8fb1f099e829fd9487f63e73704a3d4e49b30fd3b623eeec4e1102" name="postgresql96-contrib" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="00beb2bb2cf9650c5493c012068388d79965647d18822b130dda673d7395fcea" name="postgresql96-contrib-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="6279ae1ae419146f903913d9ce6c99554c88011c56a3e9de90a176d349804e82" name="postgresql96-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="382df5513ad17a3a04284a4afba5998f6c8a1891ada83d26e05aa34c050c1fa4" name="postgresql96-debugsource" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="2dd3c9a4ced92a5ca12415f942ec4352179c7118e66fd7cd245c341aa83b2041" name="postgresql96-devel" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="10.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="84d867be30e503c5b6fe3d164ba73c21d116b82d9117d46a07c18eabd9888c30" name="postgresql96-devel-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="10.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="7f4800d72109515195e12f6d1afb4c779c043ef4519932c6d9e4f3b2ecf54d43" name="postgresql96-docs" arch="noarch">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="5c99844cab53cbd52d648c58e1702552d0565981a550a6161adb890ea59ad5d0" name="postgresql96-ip4r" arch="src">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="554ac63526a0017f47ebc6f0f406183f3cdc1bc72f5db69e408c014f780b7ef2" name="postgresql96-ip4r" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="404fdfbd7dce7186e0fc2c6575dd00ecdaa2728f375d90fc055850f61aeef385" name="postgresql96-ip4r-debuginfo" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="baa6cd12e54f41ad1b76e040855e8b80afa58bd576fc2c0e6094f9d4bb7cff82" name="postgresql96-ip4r-debugsource" arch="x86_64">
  <version epoch="0" ver="2.0.2" rel="19.4"/>
  <changelog author="poeml@suse.de" date="1219838400">- create package (version 1.03)</changelog>
  <changelog author="poeml@suse.de" date="1219838401">- fix libdir path in the sql file (which was inserted as verbatim
  '$libdir')</changelog>
  <changelog author="poeml@suse.de" date="1228910400">- increase release number, so that the package supersedes the one
  that I previously built in my home:poeml project (being in
  server:database:postgresql now)</changelog>
  <changelog author="poeml@novell.com" date="1240920000">- own the /usr/lib*/pgsql directory
- remove unneeded (and non-working) directives to install the README to the
  documentation directory</changelog>
  <changelog author="poeml@suse.de" date="1246622400">- update to 1.04:
  Updates for 8.4. Minor changes for 8.4 GiST indexing.</changelog>
  <changelog author="mrueckert@suse.de" date="1288958400">- update to 1.05
  fix building with 9.0</changelog>
  <changelog author="lars@linux-schulserver.de" date="1399291200">- update to 2.0:
  + IPv6 support added, with many new types.
- using ip4r-extension-2.0 download on pg versions 9.1 and later
  to make use of the CREATE EXTENSION mechanism either for new
  installs or upgrades of ip4r-1.x versions.
- specfile cleanup
- place the ip4r.so file in the libdir of the server version used
  to built the module
- use the pre_checkin.sh from tigerfoot for building this extension
  for all versions</changelog>
  <changelog author="mrueckert@suse.de" date="1413806400">- fix installing of the extension support files</changelog>
  <changelog author="mrueckert@suse.de" date="1413806401">- update to 2.0.2
  bugfixes and switching to 9.1+ extensions style by default.</changelog>
</package>
<package pkgid="c2ea1cf3233051b204e0a38d97fd1c1dbc4f41d640239514d7d9dba6aaa3e2f0" name="postgresql96-libs" arch="src">
  <version epoch="0" ver="9.6.3" rel="10.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="41ced6046bc3e1da1cd6991fd15105e5aabde501c90c98fee4b8f36fb91499c5" name="postgresql96-libs-debugsource" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="10.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="18c7400f414a79e7db8dfc205f6f24431758328e92e7622042d6ac438db11910" name="postgresql96-pgpool-II" arch="src">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="52a37c6f1cf2117a8df33d690d46199fe32d8d535764bbfd69f52cde87b44dd0" name="postgresql96-pgpool-II" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="5499aee6184f50cf72ce0137a72795858b28e98da826b274a38624c38f835d07" name="postgresql96-pgpool-II-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="e1529d4f29152925ec59cd434a772c91905f013a2ecd0ffb2294d123226ed238" name="postgresql96-pgpool-II-debugsource" arch="x86_64">
  <version epoch="0" ver="3.6.1" rel="8.1"/>
  <changelog author="darin@darins.net" date="1406116800">- Add libmemcache support for openSUSE</changelog>
  <changelog author="mrueckert@suse.de" date="1417176000">- Update to 3.4.0
  see /usr/share/doc/packges/pgpool-II/NEWS for the details
- pgpool-II-3.4.0_64bit.patch
  fixes 2 64bit build issues: missing header file for postgresql
  function and some weird data type handling with pointers and
  integers
- Added pgpool-II-3.4.0_build_failed_with_memcached.patch:
  pulled from git: fixes issue with libmemcached on newer distros
- clean up
  - install pam file
  - cleaned up duplicated documentation files
- add systemd support</changelog>
  <changelog author="mrueckert@suse.de" date="1417435200">- run as restricted user pgpool:pgpool also with systemd</changelog>
  <changelog author="mrueckert@suse.de" date="1417435201">- add reload support to the systemd file
- set restart=always for the service</changelog>
  <changelog author="mrueckert@suse.de" date="1417435202">- forgot the systemd requires</changelog>
  <changelog author="mrueckert@suse.de" date="1417521600">- make sure also pcp is only bound to localhost by default</changelog>
  <changelog author="mrueckert@suse.de" date="1424692800">- add buildrequires on postgresqlXY-server for directory ownership</changelog>
  <changelog author="mrueckert@suse.de" date="1431345600">- update to 3.4.2
  - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
    (Nozomi Anzai)
  - Fix to reset on_exit call back functions in exec_if_cmd and
    exec_ping worker processes (Muhammad Usama) exec_if and
    exec_ping child processes were inheriting the parent exit
    callback functions which could result in undesired behavior if
    one of these commands fails. Fixed by adding on_exit_reset() at
    child start-up in both processes.
  - Fix to use void * type for receiving return value of thread
    function (Yugo Nagata) Previously int type was used and this
    could occur stack buffer overflow. This caused an infinity loop
    of ping error at bringing up or down VIP.
  - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog
    processes (Yugo Nagata) When using waitpid, it isn't necessary
    to set SIGCHLD to SIG_IGN.  Rather, it is harmful, and due to
    this it was regarded that ping command exited abnormally in
    error even when this succeeded.
  - Fix to use waitpid instead of wait in exec_ifconifg (Yugo
    Nagata)
  - Remove an unnecessary include directive (Yugo Nagata)
  - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii) This is used
    in show pool_status command and limits the length of parameter
    description.  Unfortunately recovery_timeout description is 64
    chars, which is 1 byte longer than former definition of the
    macro.
  - doc: Update document of condition for load balancig (Yugo
    Nagata) Load balancing is possible in an explicit transaction
    block even in replication mode since 3.3.0.
  - Support SSL certificate chains in the certificate file for
    incoming frontend connections (Muhammad Usama)
  - Use to_regclass if available in time stamp rewriting in
    replication mode (Tatsuo Ishii)
  - Fix to not emits a fatal error message when clear text password
    auth is used (Muhammad Usama) The problem was introduced in
    pgpool-II after inclusion of exception manager. EOF on the
    frontend connection during client authentication should not be
    treated as an error when the password authentication method is
    used. psql disconnects from the server in such case to get the
    password from the terminal, reconnects and sends the read
    password to server.
  - previous session for the same child had exited because of some
    ERROR.  (Muhammad Usama)
  - Fix a hang when an error occurs in a transaction block with
    replication mode (Yugo Nagata) When an error occurs at a
    backend node in a transaction block with replication mode,
    pgpool-II sends an invalid query to other backends to sync
    transaction states. However, previously, this was not sent to
    master node, and pgpool-II was waiting for master's response
    forever.
  - Fix a problem with pcp_detach_node about graceful node detach
    (Muhammad Usama) When graceful node detach is requested
    gracefully, pcp_detach_node should check if it is allowed to
    process detach_node command on the particular node before
    blocking the incoming connections and closing the existing
    connections.
  - doc: Update table and flowchart of where a query should be sent
    to (Yugo Nagata)
  - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix a compilation issue about sighandler_t type on BSD variants
    (Muhammad Usama)
- changes from 3.4.1
  - RPM: Add to support for memcached. (Tatsuo Ishii)
  - Fix number of parameters of pgpool_recovery from 3 to 4.
    (Tatsuo Ishii) This really should be done before releasing
    3.4.0.
  - test: Allow pgpool_setup to set configuration file directory by
    setting environment variable PGPOOLDIR (Tatsuo Ishii)
  - RPM: Rename RPM file (Yugo Nagata) Rename filename to include
    the RHEL version number like PostgreSQL's official RPM file.
    (e.g. pgpool-II-pg93-3.4.0-2pgdg.rhel6.x86_64.rpm)
  - Fix node id range check bug in trigger_failover_command().
    (Tatsuo Ishii) The node id should be lower than NUM_BACKENDS.
    Probably harmless since callers never pass node ids greater or
    equal to NUM_BACKENDS.
  - Fix occasional stuck that occures when a NOTIFY message is sent
    from a backend. (Muhammad Usama) The issue happens in master
    slave mode with load balancing when the client is doing
    extended query messaging.  per bug #116
    http://www.pgpool.net/mantisbt/view.php?id=116
  - test: Fix failover script of pgpool_setup to use absolute path
    to the database cluster (Tatsuo Ishii)
  - test: Reorganize port numbers assigned in pgpool_setup (Tatsuo
    Ishii) Assign base port (11000 by default) to pgpool, base port
    + 1 to pcp, port + 2 to PostgreSQL node0, port + 3 to
    PostgreSQL node1 and so on.
  - Fix a bug that pgpool-II 3.4 can't cancel query (Muhammad
    Usama)
  - test: Add regression test for cancelling query (Muhammad Usama)
  - Fix to not use non-thread-safe APIs in thread functions
    (Muhammad Usama) pgpool-II has borrowed the Memory and
    Exception managers from PostgreSQL which never utilizes the
    threads so its APIs are not thread safe.  Previously, those API
    functions which manipulate the global variables in thread
    functions, and it caused to undefined behavior or a
    segmentation fault. Especially, the main process could die
    silently.
  - test: Add memory leak regression test (Tatsuo Ishii)
  - Fix a memory leak with long-lived connections (Muhammad Usama)
    Problem reporeted in [pgpool-general: 3325].
  - Change the log level of "Frontend Terminated" message to DEBUG1
    from LOG (Muhammad Usama)
  - Fix ill signal befavior of SIGCHLD in exec_ifconfig() (Tatsuo
    Ishii) For some reason SIGCHLD was set to SIG_IGN *and* tries
    to wait child process which always fails because SIGCHLD is
    never delivered.  Due to this "ifconfig up" fails when
    switching to watchdog master.  See "[pgpool-general: 3310] for
    more details.
  - Allow $_IP_$ having address prefix in if_up_cmd and if_down_cmd
    (Muhammad Usama) Previously, it is assumed that "$_IP_$"
    keyword will always have a white space at the end, and when
    "$_IP_$" has address prefix (e.g.  $_IP_$/24), this prefix was
    ignored.  Per bug #122.
    http://www.pgpool.net/mantisbt/view.php?id=122
  - Fix to not send signal to init process (Muhammad Usama) This is
    more of a guard against a situation where a crash of the pgpool
    main process can make the child processes to send the signal to
    system's init process.  Per bug #119.
    http://www.pgpool.net/mantisbt/view.php?id=119
  - RPM: Fix "error: Installed (but unpackaged) file(s) found"
    while creating RPMs for PostgreSQL 9.4 (Tatsuo Ishii)
  - Allow "show pool_nodes" to print node ids having more than one
    digits (Muhammad Usama) Problem reported in [pgpool-general:
    3374].
  - Prevent "WARNING: failed to execute regex matching, pattern is
    NULL" message that could happen when application name is not
    set in the old clients (Tatsuo Ishii)
  - Fix pgpool main process to shutdown in case of child process
    start-up failures (Muhammad Usama) Problem rported in
    [pgpool-general: 3358].
  - Fix a segmentation fault that could happen in child process
    error (Muhammad Usama) Problem reported in [pgpool-general:
    3377].
  - Fix occasional failure in regression test '004.watchdog' (Yugo
    Nagata) The patch provided by uehara in bug #127.
    http://www.pgpool.net/mantisbt/view.php?id=127
  - Fix client connection leak (Tatsuo Ishii) Since 3.4.0 pgpool-II
    child does not close the connection to client when it ends the
    session.  This leads to serious "CLOSE_WAIT" flood, which makes
    pgpool-II unusable since no new connection from clients
    accepted.  Problem reported by Pablo Sanchez in
    [pgpool-general: 3394].
  - Restore SIGCHLD handler to its original after executing
    if_up/down_cmd (Yugo Nagata) Previously SIGCHLD was set to
    SIGIGN always after if_up/down_cmd.  This led to a incorrect
    error handling of ping or other commands execution, and warning
    messages were output to log even when the command exited
    successfully.
  - RPM: Add pgpool.service for systemd in RHEL/CentOS 7 (Nozomi
    Anzai)
  - Fix process termination after several reload with
    enabled_pool_hba (Muhammad Usama)
  - Tighten up checking for app_name_redirect_preference_list and
    database_redirect_preference_list (Tatsuo Ishii) Before empty
    application name or database name or invalid DB node number
    were silently accepted. Now they are strictly checked and let
    raise fatal error when starting up.  Problem reported in
    [pgpool-general-jp: 1337].
  - RPM: Change to use systemd if it is available (Nozomi Anzai)
  - Fix the behavior of "client_min_messages" configuration
    parameter (Muhammad Usama) This parameter controls the minimum
    message levels to be sent to the frontend. Previously,
    regardless of the value of the parameter all the messages with
    severity less than NOTICE level were not being forwarded to the
    client.
- update pgpooladmin to 3.4.1
  - Fix installer to allow to choose 3.4 version (Tatsuo Ishii)
- dropped pgpool-II-3.4.0_build_failed_with_memcached.patch
- replaced pgpool-II-3.4.0_64bit.patch with
  pgpool-II-3.4.2_64bit_issue.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1439467200">- update to version 3.4.3
  - Fix "cannot find xlog functions" error in pgpool-recovery
    (Muhammad Usama) The argument data type of PostgreSQL's
    pg_xlogfile_name() function has been changed from text to
    pg_lsn since PostgreSQL 9.4. And pgpool-recovery was still
    trying to locate the function by old signature.
  - Fix problem with memory cache invalidation (Muhammad Usama) The
    internal buffer for storing the table oids needs to be homed in
    long living memory context as it has to survive throughout the
    child life.  See [pgpool-general: 3643] for details.
  - Pass empty string parameters in failover command when pgpool-II
    does not have a value for any particular parameter (Muhammad
    Usama) Instead of omitting the values for the parameters when
    pgpool-II does not have any value for a particular parameter,
    it now passes an empty string to the failover command. This
    makes sure that failover script will always receive the exact
    number of expected parameters.
  - pgpool-II should use the local definition of snprintf functions
    only if they are not provided by OS (Muhammad Usama)
  - Add debug info to show how much shared memory is allocated
    (Tatsuo Ishii)
  - Downgrading the error level for EOF on backend connection for
    main process (Muhammad Usama) Throwing the FATAL error when EOF
    is encountered with backend is very harsh in pgpool main
    process and can cause undesirable behavior.  Downgrading it to
    simple ERROR.
  - doc: Clarify load balancing condition (Tatsuo Ishii)
  - doc: Clarify description of pcp_promote_node (Tatsuo Ishii) It
    does not actually promote PostgreSQL standby.
  - doc: Fix outdated limitation description about load balancing
    using JDBC driver (Tatsuo Ishii) Even if autocommit is false,
    load balancing is possible in certain conditions.
  - Fix a misplaced code which makes a log code unreachable and
    rephrase the log message (Muhammad Usama)
  - Fix a problem in elog.c when forwarding a message to frontend
    clients (Muhammad Usama) Error while forwarding the message to
    the frontend client can potentially cause the infinite
    recursion and terminate the child with ERRORDATA_STACK_SIZE
    exceeded error.  Fix is to check the recursion depth of
    send_message_to_frontend() function and pulling the plug if it
    is more than two levels deep.
  - Fix "select() system call interrupted" error (Tatsuo Ishii) The
    health check process complains above and then: ERROR:  failed
    to make persistent db connection DETAIL:  connection to
    host:"x.x.x.x:5432 failed However, the healthchek triggers
    neither fail over nor retrying. So, except the annoying
    messages above, everything goes well. This could occur more
    easily if 1) num_init_children is big and 2) pgpool children go
    into idle state (no query arrived from client for
    child_life_time seconds).  Original bug report is
    [pgpool-general: 3756] Connection Interrupted.  Patch created
    by Tatsuo Ishii. Enhancement from Usama.
  - Fix the case when user table includes spaces (Tatsuo Ishii) For
    example if table names including spaces are used, pgpool-II
    cannot be handled correctly by the internal functions which
    access system catalogs and it results in SQL errors. Solution
    is, to always use delimited identifier.  Per bug #136.
    http://www.pgpool.net/mantisbt/view.php?id=136 Also see
    [pgpool-general: 3818].
  - Allow to use in-memory query cache size more than 4GB (Tatsuo
    Ishii) This should have been allowed since in memory query
    cache was born.
  - Do not send a query for checking insert lock in non replication
    mode with extended query (Tatsuo Ishii)
  - Save pgpool_status to disk each time when it is changed (Tatsuo
    Ishii) Previously, pgpool-II saves pgpool_status file when
    pgpool-II explicitly is going shutdown. This is fine in most
    cases and it saves slight CPU cycles. But if pgpool-II killed
    abnormally or the system forces pgpool-II to go down by OOM
    killer, next pgpool-II restarting could load obsolete status
    file.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467201">- split out the extension building in another spec file, so we can
  build for multiple postgresql versions.</changelog>
  <changelog author="mrueckert@suse.de" date="1439467202">- use the pgpool version for the subpackage</changelog>
  <changelog author="mrueckert@suse.de" date="1454500800">- update to version 3.5.0:
  - Improved performance in extended query protocol
  - Overcoming the thundering herd problem
  - watchdog feature enhancements to be more robust and adaptable
  - PCP command enhancements
  - Import PostgreSQL 9.5 parser
  for all details see
  http://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features
  http://www.pgpool.net/docs/pgpool-II-3.5.0/NEWS.txt
- update pgpooladmin to version 3.5.0:
  pgpoolAdmin 3.5 adopts pgpool-II 3.5.
  - New features
  - Add new parameters for pgpool-II 3.5 (Nozomi Anzai)
    if_cmd_path, health_check_database, pcp_listen_addresses,
    search_primary_node_timeout, serialize_accept,
    sr_check_database, wd_de_escalation_command,
    wd_ipc_socket_dir, wd_priority, wd_monitoring_interfaces_list
  - Adopt to new pcp command usage (Nozomi Anzai)
  - Adopt pcp_watchdog_info in ver3.5 (Nozomi Anzai)
  - Add Chinese message catalogs (pengbo)
  - Adopt Spanish translation (Nozomi Anzai) Patch contributed by
    Rodrigo Ramirez Norambuena
  - Bug fixes
  - Add selected attribute to &lt;select&gt; of "pgpool-II version"
    (Nozomi Anzai)
  - Modified installer to check if pgsql extension is loaded
    (Nozomi Anzai) Patch contributed by Rodrigo Ramirez
    Norambuena
  - Define a new error code "e1013" and fix to return it if
    pcp_watchdog_info failed (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=149</changelog>
  <changelog author="mrueckert@suse.de" date="1454500801">- drop pgpool-II-3.4.2_64bit_issue.patch:
  included upstream
- added pgpool-II-3.5.0_no_dev_rpath.patch:
  drop prefix statement from pgpool_adm/Makefile which leads to
  unwanted/broken rpath</changelog>
  <changelog author="mrueckert@suse.de" date="1454587200">- update pgpool-II_conf.patch
  fix pcp socket path</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.5.1
  - Bug fixes
  - Add some warning messages for wd_authkey hash calculation
    failure (Yugo Nagata) Sometimes wd_authkey calculation fails
    for some reason other than authkey mismatch. The additional
    messages make these distingushable for each other.
  - test: Fix regression test to check timeout of each test (Yugo
    Nagata)
  - test: Allow timeout value to be specified by the command
    option (Yugo Nagata)
  - Fix compile issue on FreeBSD (Muhammad Usama) Added missing
    include files.  Per bug #166. The patch is contributed by the
    bug reporter and enhanced a little by Usama.
  - test: Fix test/regression/clean.sh to remove binary files of
    010.rewrite_timestamp test (Yugo Nagata)
  - Fix memorry leak reported by Coverity (CID 1350095) (Yugo
    Nagata)
  - Fixing pgpool-recovery module compilation issue with
    PostgreSQL 9.6 (Muhammad Usama) Incorporating the change of
    function signature for GetConfigOption..() functions in
    PostgreSQL 9.6.
  - Fix to properly process an empty query that has only comments
    (Tatsuo Ishii) Pgpool-II recognized an empty query, for
    example "/* DBD::Pg ping test v3.5.3 */" (note that it has no
    ';') as an error and emits message "Unable to parse the
    query". This is because raw_parser() cannot distinguish an
    empty query from an error query due to the poor API design.
    To fix this new out parameter "*error" added to the function.
    If an error occurred, the variable is set to true and caller
    can know the reason why raw_parser() returns NIL is because
    of an error query or an empty query.  Per bug #154. See
    [pgpool-hackers: 1359] for additional information.
  - Fix a reset query stuck problem (Muhammad Usama) The solution
    is to report FRONTEND_ERROR instead of simple ERROR when
    pool_flush on front-end socket fails.  The original report is
    [pgpool-general: 4265] Pgpool - connection hangs in DISCARD
    ALL The patch was generated by Usama and Pawel
    Ufnalewski&lt;archon@foap.com&gt;, and Gerhard Wiesinger
    &lt;lists@wiesinger.com&gt; helped to verify and test the fix.
  - Fix a reset query stuck problem (Tatsuo Ishii) After
    receiving X message from frontend, if pgpool-II detects EOF
    on the connection before sending reset query, pgpool-II could
    wait for a response from backend which had not received the
    reset query.  To fix this, if EOF received, treat this as
    FRONTEND_ERROR, rather than ERROR.  See "[pgpool-hackers:
    1440] Yet another reset query stuck problem" for more
    details.
  - Fix query stuck problems in streaming replication mode with
    extended protocol queries (Tatsuo Ishii) This fix is for both
    bug #167 and #168.
  - Fix pgpool hung after receiving error state from backend
    (Tatsuo Ishii) This could happend if we execute an extended
    protocol query and it fails.  Per bug #169.
  - Fix bug that child processes exit and are not re-spawned
    (Muhammad Usama) The problem was due to a logical mistake in
    the code for checking the exiting child process type when the
    watchdog is enabled. Also the severity of the message emitted
    for child exits due to max connection reached from FATAL to
    LOG.  Per [pgpool-general: 4519] Worker Processes Exit and
    Are Not Re-spawned
  - Fix typo in configure (Tatsuo Ishii) Patch provided by Thomas
    Munro.
  - doc: Change description of backend_flag (Tatsuo Ishii) It is
    pointed out that restarting pgpool-II is not necessary.  Per
    [pgpool-general-jp: 1394].
  - doc: Fix installation procedure. (Tatsuo Ishii) With
    PostgreSQL 9.4 or later, installing pgpool_regclass is not
    needed.
  - test: Fix pgpool_setup to not confuse log output (Tatsuo
    Ishii) Before it simply redirects stdout and stderr of pgpool
    processes to a log file. This could cause the log contents
    being garbled or even missed because of race condition caused
    by multiple process being writing concurrently.  To fix this,
    pgpool_setup now generates startall script in which pgpool
    sends stdout/stderr to cat command by pipe, and cat writes to
    the log file.
  - Fix to validate the PCP packet length (Muhammad Usama)
    Without the validation check, a malformed PCP packet can
    crash the PCP child and/or can run the server out of memory
    by sending the packet with a very large data size.
- update admin to 3.5.1
  - Show the path to .pcppass (Nozomi Anzai)
  - Fix not to confirm  the status of "pcp_systemdb_info" command
    if the version is 3.5 [pgpool-general: 4427] (Nozomi Anzai)
  - Add chinese templates help (pengbo)
  - Change the chinese message catalog (pengbo)
  - Fix the argument's name (Nozomi Anzai)
    http://www.pgpool.net/mantisbt/view.php?id=171
- drop to pgpool-II-3.5.0_no_dev_rpath.patch</changelog>
  <changelog author="mrueckert@suse.de" date="1462795200">- update to 3.5.2
  - Bug fixes
  - Fix for segfault during trusted_servers check (Muhammad
    Usama) PostgreSQL's memory and exception manager APIs adopted
    by the pgpool 3.4 are not thread safe and are causing the
    segmentation fault in the watchdog lifecheck process, as it
    uses the threads to ping configured trusted hosts for
    checking the upstream connections.  Fix is to remove threads
    and use the child process approach instead.  See
    [pgpool-general: 4569] for more details.
  - Removing the limit on the maximum number of items in the
    black_function_list and white_function_list lists (Muhammad
    Usama) extract_string_tokens in pool_config uses the fixed
    size malloc on the array to hold the
    black_function_list/white_function_list items.  This imposes
    a limit of maximum items in these lists.  The fix is to use
    realloc to increase the array size when it gets full.
  - Fix check "PCP Directory" in "Parameter Setting" in install
    (Nozomi Anzai) The command "pcp_system_info" was discarded in
    3.5, but pgpoolAdmin still confirmed if it existed.
    Per bug #187.
  - Fix extended protocol hang with empty query (Tatsuo Ishii)
    The fixes related to extended protocol cases in 3.5.1 broke
    the case of empty query.  In this case backend replies with
    "empty query response" which is same meaning as a command
    complete message. Problem is, when empty query response is
    received, pgpool does not reset the query in progress flag
    thus keeps on waiting for backend. However, backend will not
    send the ready for query message until it receives a sync
    message. Fix is, resetting the in progress flag after
    receiving the empty query response and reads from frontend
    expecting it sends a sync message.  Per bug #190.
  - Redirect all user queries to primary server (Tatsuo Ishii) Up
    to now some user queries are sent to other than the primary
    server even if load_balance_mode = off. This commit changes
    the behavior: if load_balance_mode = off in streaming
    replication mode, now all the user queries are sent to the
    primary server only. Per bug #189.
  - Change the PID length of pcp_proc_count command result to 6
    characters long (Bo Peng) If the pgpool process ID are over 5
    characters, the 6th character of each process ID will be
    removed. This commit changes the process ID length of
    pcp_proc_count command result to 6 characters long.
    Per bug #188.</changelog>
  <changelog author="mrueckert@suse.de" date="1467892800">- update to 3.5.3
  - New features
  - Allow to access to pgpool while doing health checking (Tatsuo
    Ishii)
    Currently any attempt to connect to pgpool fails if pgpool is
    doing health check against failed node even if
    fail_over_on_backend_error is off because pgpool child first
    tries to connect to all backend including the failed one and
    exits if it fails to connect to a backend (of course it
    fails). This is a temporary situation and will be resolved
    before pgpool executes failover. However if the health check
    is retrying, the temporary situation keeps longer depending
    on the setting of health_check_max_retries and
    health_check_retry_delay. This is not good. Attached patch
    tries to mitigate the problem:
  - When an attempt to connect to backend fails, give up
    connecting to the failed node and skip to other node,
    rather than exiting the process if operating in streaming
    replication mode and the node is not primary node.
  - Mark the local status of the failed node to "down".
  - This will let the primary node be selected as a load
    balance node and every queries will be sent to the primary
    node. If there's other healthy standby nodes, one of them
    will be chosen as the load balance node.
  - After the session is over, the child process will suicide
    to not retain the local status.
    Per [pgpool-hackers: 1531].
  - Bug fixes
  - Fix is_set_transaction_serializable() when SET
    default_transaction_isolation TO 'serializable'. (Bo Peng)
    SET default_transaction_isolation TO 'serializable' is sent
    to not only primary but also to standby server in streaming
    replication mode, and this causes an error. Fix is, in
    streaming replication mode, SET default_transaction_isolation
    TO 'serializable' is sent only to the primary server.
    See bug 191 for related info.
  - Fix Chinese documetation bug about raw mode (Yugo Nagata, Bo
    Peng) Connection pool is avalilable in raw mode.
  - Fix confusing comments in pgpool.conf (Tatsuo Ishii)
  - Fix extended protocol handling in raw mode (Tatsuo Ishii)
    Bug152 reveals that extended protocol handling in raw mode
    (actually other than in stream mode) was wrong in Describe()
    and Close().  Unlike stream mode, they should wait for
    backend response.
    See bug 152 for related info.
  - Permit pgpool to support multiple SSL cipher protocols
    (Muhammad Usama)
    Currently TLSv1_method() is used to initialize the SSL
    context, that puts an unnecessary limitation to allow only
    TLSv1 protocol for SSL communication.  While postgreSQL
    supports other ciphers protocols as well. The commit changes
    the above and initializes the SSLSession using the
    SSLv23_method() (same is also used by PostgreSQL). Because it
    can negotiate the use of the highest mutually supported
    protocol version and remove the limitation of one specific
    protocol version.
  - If statement timeout is enabled on backend and do_query()
    sends a (Tatsuo Ishii) query to primary node, and all of
    following user queries are sent to standby, it is possible
    that the next command, for example END, could cause a
    statement timeout error on the primary, and a kind mismatch
    error on pgpool-II is raised.
    This fix tries to mitigate the problem by sending sync
    message instead of flush message in do_query(), expecting
    that the sync message reset the statement timeout timer if we
    are in an explicit transaction. We cannot use this technique
    for implicit transaction case, because the sync message
    removes the unnamed portal if there's any.
    Plus, pg_stat_statement will no longer show the query issued
    by do_query() as "running".
    See bug 194 for related info.
  - Deal with the case when the primary is not node 0 in
    streaming replication mode.  (Tatsuo Ishii)
    http://www.pgpool.net/mantisbt/view.php?id=194#c837 reported
    that if primary is not node 0, then statement timeout could
    occur even after bug194-3.3.diff was applied. After some
    investigation, it appeared that MASTER macro could return
    other than primary or load balance node, which was not
    supposed to happen, thus do_query() sends queries to wrong
    node (this is not clear from the report but I confirmed it in
    my investigation).
    pool_virtual_master_db_node_id(), which is called in MASTER
    macro returns query_context-&gt;virtual_master_node_id if query
    context exists. This could return wrong node if the variable
    has not been set yet. To fix this, the function is modified:
    if the variable is not either load balance node or primary
    node, the primary node id is returned.
  - Fix a posible hang during health checking (Yugo Nagata)
    Helath checking was hang when any data wasn't sent from
    backend after connect(2) succeeded. To fix this,
    pool_check_fd() returns 1 when select(2) exits with EINTR due
    to SIGALRM while health checkking is performed.
    Reported and patch provided by harukat and some modification
    by Yugo.
    See bug 204 for related info.
  - change the Makefile under this directory src/sql/,that is
    proposed by (Bo Peng) [pgpool-hackers: 1611]
  - fix for 0000197: pgpool hangs connections to database..
    (Muhammad Usama)
    The client connection was getting stuck when backend node and
    remote pgpool-II node becomes unavailable at the same time.
    The reason was a missing command timeout handling in the
    function that sends the IPC commands to watchdog.
  - Fix bug with load balance node id info on shmem
    (Tatsuo Ishii)
    There are few places where the load balance node was
    mistakenly put on wrong place. It should be placed on:
    ConnectionInfo *con_info[child id, connection pool_id,
    backend id].load_balancing_node].  In fact it was placed on:
  * con_info[child id, connection pool_id, 0].load_balancing_node].
    As long as the backend id in question is 0, it is ok. However
    while testing pgpool-II 3.6's enhancement regarding failover,
    if primary node is 1 (which is the load balance node) and
    standby is 0, a client connecting to node 1 is disconnected
    when failover happens on node 0. This is unexpected and the
    bug was revealed.
    It seems the bug was there since long time ago but it had not
    found until today by the reason above.
  - Fixing coverity scan reported issues. (Muhammad Usama)</changelog>
  <changelog author="mrueckert@suse.de" date="1475496000">- update to 3.5.4
  - Fix buffer over run problem in "show pool_nodes". (Tatsuo
    Ishii) While processing "show pool_nodes", the buffer for
    hostname was too short. It should be same size as the buffer
    used for pgpool.conf.  Problem reported by a twitter user who
    is using pgpool on AWS (which could have very long hostname).
  - Fix usage of wait(2) in pgpool main process. (Tatsuo Ishii) The
    usage of wait(2) in pgpool main could cause infinite wait in
    the system call. Solution is, to use waitpid(2) instead of
    wait(2).
  - Save and restore errno in each signal handler. (Tatsuo Ishii)
  - Fix handling of pcp_listen_addresses config parameter.
    (Muhammad Usama)
  - Fix "kind mismatch" error message in pgpool. (Muhammad Usama)
    Many of "kind mismatch..." errors are caused by notice/warning
    messages produced by one or more of the DB nodes. In this case
    now Pgpool-II forwards the messages to frontend, rather than
    throwing the "kind mismatch..." error. This would reduce the
    chance of "kind mismatch..."  errors.  See [pgpool-hackers:
    1501] for more details.
  - Replace "MAJOR" macro to prevent occasional failure. (Tatsuo
    Ishii) The macro calls pool_virtual_master_db_node_id() and
    then access backend-&gt;slots[id]-&gt;con using the node id returned.
    In rare cases, it could point to 0 (in case when the DB node is
    not connected), which gives access to con-&gt;major, then it
    causes a segfault.  See bug 225 for related info.
  - Fixing a coding mistake in watchdog code. (Muhammad Usama)
    wd_issue_failover_lock_command() function is supposed to
    forward command type passed in as an argument to the
    wd_send_failover_sync_command() function instead it was passing
    the NODE_FAILBACK_CMD command type.  The commit also contains
    some log message enhancements.
  - doc : Fixing a typo in english doc (Muhammad Usama)
  - Fix for bun 215 that pgpool doesn't escalate ip in case of
    another node inavailability.  (Muhammad Usama) The heartbeat
    receiver fails to identify the heartbeat sender watchdog node
    when the heartbeat destination is specified in terms of an IP
    address while wd_hostname is configured as a hostname string or
    vice versa.  See bug 215 for related info.
  - Fix for bug of inconsistent status of Postgresql nodes in
    Pgpool instances after restart.(Muhammad Usama) Watchdog does
    not synchronize status.  See bug 218 for related info.
  - SIGUSR1 signal handler should be installed before watchdog
    initialization.  (Muhammad Usama) Since there can be a case
    where a failover request from other watchdog nodes arrive at
    the same time when the watchdog has just been initialized, and
    if we wait any longer to install a SIGUSR1 signal handler, it
    can result in a potential crash.
  - Fix for bug 228 that pgpool doesn't de-escalate IP in case
    network restored.  (Muhammad Usama) See bug 228 for related
    info.
  - Fix hang when portal suspend received. (Tatsuo Ishii) See bug
    230 for related info.
  - test : Add regression test for bug 230. (Tatsuo Ishii)
  - Fixing a typo in the log message. (Muhammad Usama)
  - Fixing the error messages when the socket operation fails.
    (Muhammad Usama)
  - Tighten up health check timer expired condition in
    pool_check_fd(). (Muhammad Usama)
  - doc : Add comment to the document about connection_cache.
    (Tatsuo Ishii)
  - Fix Handling of pcp_socket_dir was missing from
    pool_get_config(). (Muhammad Usama)
  - doc : Fix Japanese document typo. (Bo Peng)
  - Fix "out of memory" by using "pg_md5 -m".(Muhammad Usama) See
    bug 236 for related info.
  - Fix for 237 that Pgpool-II fails to start if listen_addresses
    is empty string.  (Muhammad Usama) The socket descriptor array
    (fds[]) was not getting the array end marker when TCP listen
    addresses are not used.  See bug 237 for related info.</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.6.1
  - Improve the behavior of fail-over. In the steaming replication
    mode, client sessions will not be disconnected when a fail-over
    occurs any more if the session does not use the failed standby
    server. If the primary server goes down, still all sessions
    will be disconnected.  Also it is possible to connect to
    Pgpool-II even if it is doing health checking retries. Before
    all attempt of connecting to Pgpool-II failed while doing
    health checking retries.
  - New PGPOOL SET command has been introduced. Certain
    configuration parameters now can be changed on the fly in a
    session.
  - Watchdog is significantly enhanced. It becomes more reliable
    than previous releases.
  - Handling of extended query protocol (e.g. used by Java
    applications) in streaming replication mode speeds up if many
    rows are returned in a result set.
  - Import parser of PostgreSQL 9.6.
  - In some cases pg_terminate_backend() now does not trigger a
    fail-over.
  - Change documentation format from raw HTML to SGML.
  For all the details see /usr/share/doc/packages/pgpool-II/NEWS</changelog>
  <changelog author="mrueckert@suse.de" date="1486728001">- added pgpool-II-3.6.1_implicit.patch</changelog>
</package>
<package pkgid="be3c2ea6c6b7f531bc5255882c06f63463e5ac9047fe56ca2e50a382d63dc773" name="postgresql96-plperl" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="f8f4acebe5438d100ee2e94d214099186eb388178bb992b4c08d2e40ba12bd37" name="postgresql96-plperl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="69751c3bcc98099387c54038e81ccab541ac840942b687d44f5a9ddedd9c132d" name="postgresql96-plpython" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="c24467223928f436f92a6a9606d581b8963a219a7bb4b5e66e4a612eb9d04538" name="postgresql96-plpython-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="c7175b8290b9f54d00ee5f10ab0112f5166bcdcc89e0c640c3f8ce116d6a80ed" name="postgresql96-plr" arch="src">
  <version epoch="0" ver="8.3.0.17" rel="7.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
  <changelog author="jengelh@inai.de" date="1490270400">- Avoid unnecessary %__-type macro indirection</changelog>
</package>
<package pkgid="8a1dc1c105ccd27a6cc58783e9e21eb9c4a7057995180b718b7757f353effed3" name="postgresql96-plr" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="7.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
  <changelog author="jengelh@inai.de" date="1490270400">- Avoid unnecessary %__-type macro indirection</changelog>
</package>
<package pkgid="4ef5df9a25fdbcae3261a1f3a1cf6cd45a7a180d3b10850706cfd4f56a0a262e" name="postgresql96-plr-debuginfo" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="7.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
  <changelog author="jengelh@inai.de" date="1490270400">- Avoid unnecessary %__-type macro indirection</changelog>
</package>
<package pkgid="b46aa1fc3b6fbb5f7d52403a717ebf8adfe076d4f00d05909c292ad149984c26" name="postgresql96-plr-debugsource" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="7.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
  <changelog author="jengelh@inai.de" date="1490270400">- Avoid unnecessary %__-type macro indirection</changelog>
</package>
<package pkgid="d3f355a5d006c4bb8ee1d4546f611f9ff9bd6fbb05d8fe7b8858bfa5b3c5fda1" name="postgresql96-plr-doc" arch="x86_64">
  <version epoch="0" ver="8.3.0.17" rel="7.1"/>
  <changelog author="bruno@ioda-net.ch" date="1307534400">- First spec version for obs</changelog>
  <changelog author="bruno@ioda-net.ch" date="1307966400">- Try to fix folders installation</changelog>
  <changelog author="bruno@ioda-net.ch" date="1308312000">- Fixed spurious perms</changelog>
  <changelog author="bruno@ioda-net.ch" date="1318852800">* Upgrade to 8.3.0.13
  - Fix Makefile so that msvc scripts can process it successfully
  - Add support for pgsql 9.1 CREATE EXTENSION
  - Put in safeguard to prevent attempted return of non-data (e.g.
  closure) types from R unless the pg return type is BYTEA
  - Correct thinko from earlier pass-by-val array optimization
  - Fix crashbug related to conversion of R data.frame to Postgres
  array on function return
  - Add plr_version() function: outputs a version string
  - New feature: allow PL/R functions to be declared and used
  as WINDOW functions
  - Minor fixes for compiler warnings by updated gcc
  - Fix missing calls to UNPROTECT. Report and patch by Ben Leiting.
  - Take SIGINT back into Postgres control from R. Report and test case
  by Terry Schmitt.
  - Don't try to free an array element value when the array element is NULL
  - Allow pg.spi.prepare/pg.spi.execp to use parameters which are 1D arrays-</changelog>
  <changelog author="bruno@ioda-net.ch" date="1330776000">- Split documentation to postgresql-plr
- Add more informations (first step and test to readme.SUSE)
- Try to use -rpath (following darix advise) but no success</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333108800">- Fix installation directory : goes to extension now
- Added missing expected plr.out to doc as sample howto</changelog>
  <changelog author="bruno@ioda-net.ch" date="1333281600">- Fix formatting &amp; licence scheme</changelog>
  <changelog author="bruno@ioda-net.ch" date="1334577600">- Make factory happy added R-base as Build-Require</changelog>
  <changelog author="darin@darins.net" date="1357128000">* Upgrade to 8.3.0.13.1
  - Fix CREATE FUNCTION statements so that they work
  with PostgreSQL 9.2.x</changelog>
  <changelog author="bruno@ioda-net.ch" date="1374667200">- Upgrade to 8.3.0.14
  Update copyright for 2013
  Remove hack to take signal back from R interpreter (Mark Kirkwood)
  Set R_SignalHandlers = 0, the proper way to prevent R from taking signals in the first place (Mark Kirkwood)
  Adjust RPM spec file
  As of pg9.2 the syntax "LANGUAGE 'C'" no longer works. Use "LANGUAGE C" instead.
  The MacPorts installation has the header filed distributed across two different directories, so there is no single "rincludedir" to query from pkg-config. Instead, do it the proper way and ask pkg-config for the cflags, which should work for all installation variants. (Peter Eisentraut)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1380283200">- split postgresql-plr to postgresql version aligned
  postgresql91-plr linked to postgresql91
  postgresql92-plr linked to postgresql92
  postgresql93-plr linked to postgresql93</changelog>
  <changelog author="bruno@ioda-net.ch" date="1384776000">- Packaging postgresql-plr
  Added postgresql-server as BuildRequires so rpmlint doesn't complain about
  owner of postgresql base install directory</changelog>
  <changelog author="bruno@ioda-net.ch" date="1386331200">- Update to upstream 8.0.15
  Update for PostgreSQL 9.3 compatibility
  Ensure certain errors in R code do not crash postgres
  Unbreak compilation with older versions of postgres not having rangetypes
  Allow use of OUT parameters
- modified patches: redone for 8.0.15
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1390478400">- Revised year
- Added pre_checkin.sh methode to create variant packages</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423483200">- Update to upstream 8.3.0.16
  Update for PostgreSQL 9.5dev compatibility
  Update copyrights
  Add check and throw an error when don't have an expectedDesc.
  Remove autocommit setting -- it has been removed in PostgreSQL
  9.5, and it has been ineffective for a long time.
    Reported by Peter E.
  Fix RPM spec file (redhat)
- Added support to postgresql94 packages
- modified patches: redone for 8.0.16
  * patch-Makefile-ldflags.patch</changelog>
  <changelog author="bruno@ioda-net.ch" date="1423828800">- Update to last upstream tar.gz
  Due to missing root plr, and documentation (Conway)
- Removed upgrade alter extension, this doesn't work yet</changelog>
  <changelog author="bruno@ioda-net.ch" date="1450699200">- Fix postun/postin ldconfig call (see comment in sr#345782)</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484136000">- Update to 08.03.00.17 version - Bring support to postgresql96
- Packaging
  + Move source to github and adapt packaging for that
  + Add plr-US.pdf as documentation, html being not delivered
    Documentation is build outside of the package to avoid texlive
  + Redone patch-Makefile-ldflags.patch to current sources
  + Rename postgresql-plr.changes.in to postgresql-plr.changes to
    ease osc vc edition, adapt pre_checking.sh to this change.</changelog>
  <changelog author="bruno@ioda-net.ch" date="1484395200">- Undo the rename of postgresql-plr.changes.in to make happy
  factory auto-bot</changelog>
  <changelog author="jengelh@inai.de" date="1490270400">- Avoid unnecessary %__-type macro indirection</changelog>
</package>
<package pkgid="68c9e02c04c4aa5f3bdb23e1c38ac49e706a9effb21dc35d1246c6115123bbe9" name="postgresql96-pltcl" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="7f6f357fde93211709ad44dbd0ab0cc8c5a65bebf9baa26ea9737e7b46211449" name="postgresql96-pltcl-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="223c0167de897ca1e071392d80208d1db51df46c1d8e3c588c2ef20e6671dab9" name="postgresql96-repmgr" arch="src">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="1b532a5b262d1a2913125b0fdb5a7b9120756a092759c6fa1ba9d237f6414b32" name="postgresql96-repmgr" arch="x86_64">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="e7314c81a1ae15f37fd2332302184f857408406cf538f41b438d5de82b81fef3" name="postgresql96-repmgr-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="b83fa77d373d5d0097e30c16aa2180fb11753c29a6a980708369156ba0c33c94" name="postgresql96-repmgr-debugsource" arch="x86_64">
  <version epoch="0" ver="3.3" rel="1.3"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="1eb2cf2ca49099366ed07c0c710e634566c9a7bc62099c2895114022825a30ab" name="postgresql96-server" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="d6331fb1fc01bea4f5e288c718932965390c8b52baf76640321ce764a53995ac" name="postgresql96-server-debuginfo" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="6b68af63facfa6838854d11a6c219155bb13eef73ade448ad9163a9a2fa31ce1" name="postgresql96-test" arch="x86_64">
  <version epoch="0" ver="9.6.3" rel="9.1"/>
  <changelog author="max@suse.com" date="1424347200">- Align spec file with 9.3 package.
- Require systemd only where available and only for the main
  package.
- bnc#888564: Move the server socket from /tmp to /var/run to avoid
  problems with clients that use PrivateTmp.
  postgresql-var-run-socket.patch</changelog>
  <changelog author="max@suse.com" date="1435320000">- Switch from ossp-uuid to libuuid from e2fsprogs.
- Re-enable running the test suite during build.
- Bugfix release 9.4.4:
  * Fix possible failure to recover from an inconsistent database
    state.
  * Fix rare failure to invalidate relation cache init file.
  * Avoid deadlock between incoming sessions and CREATE/DROP
    DATABASE.
  * Improve planner's cost estimates for semi-joins and anti-joins
    with inner indexscans
- Bugfix release 9.4.3:
  * Avoid failures while fsync'ing data directory during crash
    restart.
  * Fix pg_get_functiondef() to show functions' LEAKPROOF property,
    if set.
  * Fix pushJsonbValue() to unpack jbvBinary objects.
- Security and bugfix release 9.4.2:
  * CVE-2015-3165, bsc#931972: Avoid possible crash when client
    disconnects just before the authentication timeout expires.
  * CVE-2015-3166, bsc#931973: Consistently check for failure of
    the *printf() family of functions.
  * CVE-2015-3167, bsc#931974: In contrib/pgcrypto, uniformly
    report decryption failures as "Wrong key or corrupt data".
  * Protect against wraparound of multixact member IDs.
- For the full release notse, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-2.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-3.html
  http://www.postgresql.org/docs/9.4/static/release-9-4-4.html</changelog>
  <changelog author="max@suse.com" date="1437480000">- Bring PostgreSQL 9.4 to SLE12 (fate#319049).</changelog>
  <changelog author="max@suse.com" date="1443441600">- Move ~postgres/.bash_profile to postgresql-server to avoid a
  file conflict between the versioned server packages.</changelog>
  <changelog author="max@suse.com" date="1444305600">- Make sure that plpgsql.h gets installed, because pldebugger
  needs it.</changelog>
  <changelog author="max@suse.com" date="1444651200">- Security and bugfix release 9.4.5:
  * CVE-2015-5289, bsc#949670: json or jsonb input values
    constructed from arbitrary user input can crash the PostgreSQL
    server and cause a denial of service.
  * CVE-2015-5288, bsc#949669: The crypt() function included with
    the optional pgCrypto extension could be exploited to read a
    few additional bytes of memory. No working exploit for this
    issue has been developed.
- For the full release notse, see:
  http://www.postgresql.org/docs/current/static/release-9-4-5.html
- Move systemd related stuff and user creation to postgresql-init.
- Remove some obsolete %suse_version conditionals
- Adjust build time dependencies.
- Fix some more rpmlint warnings.
- Relax dependency on libpq to major version.</changelog>
  <changelog author="max@suse.com" date="1455019200">- PL/Perl still needs to be linked with rpath, so that it can find
  libperl.so at runtime.
  bsc#578053, postgresql-plperl-keep-rpath.patch</changelog>
  <changelog author="max@suse.com" date="1455278400">- Security and bugfix release 9.4.6:
  * *** IMPORTANT ***
    Users of version 9.4 will need to reindex any jsonb_path_ops
    indexes they have created, in order to fix a persistent issue
    with missing index entries.
  * Fix infinite loops and buffer-overrun problems in regular
    expressions (CVE-2016-0773, bsc#966436).
  * Fix regular-expression compiler to handle loops of constraint
    arcs (CVE-2007-4772).
  * Prevent certain PL/Java parameters from being set by
    non-superusers (CVE-2016-0766, bsc#966435).
  * Fix many issues in pg_dump with specific object types
  * Prevent over-eager pushdown of HAVING clauses for
    GROUPING SETS
  * Fix deparsing error with ON CONFLICT ... WHERE clauses
  * Fix tableoid errors for postgres_fdw
  * Prevent floating-point exceptions in pgbench
  * Make \det search Foreign Table names consistently
  * Fix quoting of domain constraint names in pg_dump
  * Prevent putting expanded objects into Const nodes
  * Allow compile of PL/Java on Windows
  * Fix "unresolved symbol" errors in PL/Python execution
  * Allow Python2 and Python3 to be used in the same database
  * Add support for Python 3.5 in PL/Python
  * Fix issue with subdirectory creation during initdb
  * Make pg_ctl report status correctly on Windows
  * Suppress confusing error when using pg_receivexlog with older
    servers
  * Multiple documentation corrections and additions
  * Fix erroneous hash calculations in gin_extract_jsonb_path()
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-6.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363200">- Security and bugfix release 9.4.7: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- For the full release notes, see:
  http://www.postgresql.org/docs/9.4/static/release-9-4-7.html</changelog>
  <changelog author="mrueckert@suse.de" date="1462363201">- Security and bugfix release 9.5.2: (bnc# 978456)
  This release closes security hole CVE-2016-2193, where a query
  plan might get reused for more than one ROLE in the same session.
  This could cause the wrong set of Row Level Security (RLS)
  policies to be used for the query.
  The update also fixes CVE-2016-3065, a server crash bug triggered
  by using pageinspect with BRIN index pages. Since an attacker
  might be able to expose a few bytes of server memory, this crash
  is being treated as a security issue.
  - Fix two bugs in indexed ROW() comparisons
  - Avoid data loss due to renaming files
  - Prevent an error in rechecking rows in SELECT FOR UPDATE/SHARE
  - Fix bugs in multiple json_ and jsonb_ functions
  - Log lock waits for INSERT ON CONFLICT correctly
  - Ignore recovery_min_apply_delay until reaching a consistent
    state
  - Fix issue with pg_subtrans XID wraparound
  - Fix assorted bugs in Logical Decoding
  - Fix planner error with nested security barrier views
  - Prevent memory leak in GIN indexes
  - Fix two issues with ispell dictionaries
  - Avoid a crash on old Windows versions
  - Skip creating an erroneous delete script in pg_upgrade
  - Correctly translate empty arrays into PL/Perl
  - Make PL/Python cope with identifier names
- changes from 9.5.1 (bnc# 966435 bnc# 966436 bnc# 978323)
  This release closes security hole CVE-2016-0773, an issue with
  regular expression (regex) parsing. Prior code allowed users to
  pass in expressions which included out-of-range Unicode
  characters, triggering a backend crash. This issue is critical
  for PostgreSQL systems with untrusted users or which generate
  regexes based on user input.
  The update also fixes CVE-2016-0766, a privilege escalation issue
  for users of PL/Java. Certain custom configuration settings
  (GUCS) for PL/Java will now be modifiable only by the database
  superuser.
  In addition to the above, many other issues were patched in this
  release based on bugs reported by our users over the last few
  months. This includes multiple fixes for new features introduced
  in version 9.5.0, as well as refactoring of pg_dump to eliminate
  a number of chronic issues with backing up EXTENSIONs. Among them
  are:
  - Fix many issues in pg_dump with specific object types
  - Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  - Fix deparsing error with ON CONFLICT ... WHERE clauses
  - Fix tableoid errors for postgres_fdw
  - Prevent floating-point exceptions in pgbench
  - Make \det search Foreign Table names consistently
  - Fix quoting of domain constraint names in pg_dump
  - Prevent putting expanded objects into Const nodes
  - Allow compile of PL/Java on Windows
  - Fix "unresolved symbol" errors in PL/Python execution
  - Allow Python2 and Python3 to be used in the same database
  - Add support for Python 3.5 in PL/Python
  - Fix issue with subdirectory creation during initdb
  - Make pg_ctl report status correctly on Windows
  - Suppress confusing error when using pg_receivexlog with older
    servers
  - Multiple documentation corrections and additions
  - Fix erroneous hash calculations in gin_extract_jsonb_path()
  - This update also contains tzdata release 2016a, with updates
    for Cayman Islands, Metlakatla, Trans-Baikal Territory
    (Zabaykalsky Krai), and Pakistan.
- changes from 9.5.0
  A most-requested feature by application developers for several
  years, "UPSERT" is shorthand for "INSERT, ON CONFLICT UPDATE",
  allowing new and updated rows to be treated the same. UPSERT
  simplifies web and mobile application development by enabling the
  database to handle conflicts between concurrent data changes.
  This feature also removes the last significant barrier to
  migrating legacy MySQL applications to PostgreSQL.
  Developed over the last two years by Heroku programmer Peter
  Geoghegan, PostgreSQL's implementation of UPSERT is significantly
  more flexible and powerful than those offered by other relational
  databases. The new ON CONFLICT clause permits ignoring the new
  data, or updating different columns or relations in ways which
  will support complex ETL (Extract, Transform, Load) toolchains
  for bulk data loading. And, like all of PostgreSQL, it is
  designed to be absolutely concurrency-safe and to integrate
  with all other PostgreSQL features, including Logical
  Replication.
  PostgreSQL continues to expand database security capabilities
  with its new Row Level Security (RLS) feature. RLS implements
  true per-row and per-column data access control which integrates
  with external label-based security stacks such as SE Linux.
  PostgreSQL is already known as "the most secure by default." RLS
  cements its position as the best choice for applications with
  strong data security requirements, such as compliance with PCI,
  the European Data Protection Directive, and healthcare data
  protection standards.
  RLS is the culmination of five years of security features added
  to PostgreSQL, including extensive work by KaiGai Kohei of NEC,
  Stephen Frost of Crunchy Data, and Dean Rasheed. Through it,
  database administrators can set security "policies" which filter
  which rows particular users are allowed to update or view. Data
  security implemented this way is resistant to SQL injection
  exploits and other application-level security holes.
  PostgreSQL 9.5 includes multiple new features for bigger
  databases, and for integrating with other Big Data systems. These
  features ensure that PostgreSQL continues to have a strong role
  in the rapidly growing open source Big Data marketplace. Among
  them are:
  BRIN Indexing: This new type of index supports creating tiny, but
  effective indexes for very large, "naturally ordered" tables. For
  example, tables containing logging data with billions of rows
  could be indexed and searched in 5% of the time required by
  standard BTree indexes.
  Faster Sorts: PostgreSQL now sorts text and NUMERIC data faster,
  using an algorithm called "abbreviated keys". This makes some
  queries which need to sort large amounts of data 2X to 12X
  faster, and can speed up index creation by 20X.
  CUBE, ROLLUP and GROUPING SETS: These new standard SQL clauses
  let users produce reports with multiple levels of summarization
  in one query instead of requiring several. CUBE will also enable
  tightly integrating PostgreSQL with more Online Analytic
  Processing (OLAP) reporting tools such as Tableau.
  Foreign Data Wrappers (FDWs): These already allow using
  PostgreSQL as a query engine for other Big Data systems such as
  Hadoop and Cassandra. Version 9.5 adds IMPORT FOREIGN SCHEMA and
  JOIN pushdown making query connections to external databases both
  easier to set up and more efficient.
  TABLESAMPLE: This SQL clause allows grabbing a quick statistical
  sample of huge tables, without the need for expensive sorting.
  "The new BRIN index in PostgreSQL 9.5 is a powerful new feature
  which enables PostgreSQL to manage and index volumes of data that
  were impractical or impossible in the past. It allows scalability
  of data and performance beyond what was considered previously
  attainable with traditional relational databases and makes
  PostgreSQL a perfect solution for Big Data analytics," said Boyan
  Botev, Lead Database Administrator, Premier, Inc.
  http://www.postgresql.org/about/news/1636/
- For the full release notes, see:
  http://www.postgresql.org/docs/9.5/static/release-9-5.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-1.html
  http://www.postgresql.org/docs/9.5/static/release-9-5-2.html
- refreshed patches to match new release
  postgresql-conf.patch
  postgresql-plperl-keep-rpath.patch
  postgresql-regress.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- drop postgresql-testsuite-seclabel-location.patch:
  the dummy seclabel test is gone</changelog>
  <changelog author="mrueckert@suse.de" date="1463054400">- update to 9.6beta1
  - Major Features of 9.6
    Version 9.6 includes significant changes and exciting
    enhancements including:
  - Parallel sequential scans, joins and aggregates
  - Support for consistent, read-scaling clusters through
    multiple synchronous standbys and "remote_apply" synchronous
    commit.
  - Full text search for phrases
  - postgres_fdw can now execute sorts, joins, UPDATEs and
    DELETEs on the remote server
  - Decreased autovacuum impact on big tables by avoiding
    "refreezing" old data.
  - In particular, parallel execution should bring a noticeable
    increase in performance to supported queries.
  - Help Test for Bugs
    As with other major releases, the improvements in PostgreSQL
    include changes to large amounts of code. We count on you to
    test the altered version with your workloads and testing tools
    in order to find bugs and regressions before the release of
    PostgreSQL 9.6.0. In addition to testing that the new features
    work as documented, consider testing the following:
  - Do parallel queries actually improve performance for you?
  - Can you make parallel queries crash or lose data?
  - Do our code changes cause PostgreSQL to not function on your
    platform?
  - Does improved vacuum freezing safely reduce autovacuum of
    large tables?
  - Does phrase search return the results you expect?
    Version 9.6 Beta 1 also makes changes to the binary backup API.
    Administrators should test version 9.6 with PostgreSQL backup
    tools, including pgBackRest, Barman, WAL-E, and other packaged
    and in-house software.
    As this is a Beta, minor changes to database behaviors, feature
    details, and APIs are still possible. Your feedback and testing
    will help determine the final tweaks on the new features, so
    test soon. The quality of user testing helps determine when we
    can make a final release.
  http://www.postgresql.org/about/news/1668/
  http://www.postgresql.org/docs/devel/static/release-9-6.html
- refreshed patches to apply cleanly again:
  postgresql-plperl-keep-rpath.patch
  postgresql-testsuite-int8.sql.patch
  postgresql-testsuite-keep-results-file.patch
  postgresql-var-run-socket.patch
- regress part is disabled atm as it causes a buildfailure
- also remove static libraries in pglibdir. This release introduced
  a new file there called pgfeutils.a</changelog>
  <changelog author="mrueckert@suse.de" date="1466769600">- update to 9.6beta2
  Our users and contributors reported bugs against 9.6 beta 1, and
  some of them have been fixed in this release. This includes
  multiple fixes for failure and performance issues in parallel
  query. We urge our community to re-test to ensure that these bugs
  are actually fixed, including:
  - update most contrib extensions for parallel query
  - two fixes for pg_trgm (trigram) bugs
  - rewrite code to estimate join sizes for better performance
  - correct handling of argument and result datatypes for partial
    aggregation
  - fix lazy_scan_heap so that it won't mark pages all-frozen too
    soon
  - mark additional functions as parallel-unsafe
  - check PlaceHolderVars before pushing down a join in
    postgres_fdw
  - improve the situation for parallel query versus temp relations
  - don't generate parallel paths for rels with parallel-restricted
    outputs
  - make psql_crosstab plans more stable
  - finish loose ends for SQL ACCESS METHOD objects, including
    pg_dump
  - stop the executor if no more tuples can be sent from worker to
    leader
  - several pg_upgrade fixes to support new features
  - fix regression tests for phrase search
  - add new snapshot fields to serialize/deserialize functions
  - measure Bloom index signature-length reloption in bits, not
    words
  - many improvements to parallel regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Additionally, we've made some user-visible changes to parameters
  and functions. These may cause dump/restore between beta 1 and
  beta 2 to generate errors. This includes:
  - rename max_parallel_degree to max_parallel_workers_per_gather
  - add integrity-checking functions to pg_visibility
  - add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies
  - add pg_truncate_visibility_map function
  - add min_parallel_relation_size GUC
  - change default of backend_flush_after GUC to 0 (disabled)
  Note that some known issues remain unfixed. Before reporting a
  bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 9.6beta3
  - This included many more fixes to parallel query:
  - adding support for TABLESAMPLE
  - correcting cost data in Gather nodes
  - check parallel-safety of all appended relations
  - fix planner issues with initPlans
  - fix several issues with client_encoding
  - clean up EXPLAIN output for parallel queries
  - multiple changes to parallel aggregation internals
  - Among the other issues addressed were:
  - add conninfo field to pg_stat_wal_receiver
  - clear all-frozen visibilitymap status when locking tuples
  - correctly dump database and tablespace ACLs
  - avoid invalidating all foreign-join cached plans when user
    mappings change
  - fix nested NOT operation cleanup in tsquery
  - allow IMPORT FOREIGN SCHEMA within pl/pgsql
  - print a given subplan only once in EXPLAIN
  - change the GetForeignUpperPaths API
  - fix several issues in postgres_fdw
  - added many additional regression tests
  - many documentation updates and clarifications
  - multiple translation updates for the docs
  Due to changes in system catalogs, a pg_upgrade or dump and restore
  will be required for users migrating databases from earlier betas.
  This includes a version update to the pg_control tool, making it
  incompatible with PostgreSQL 9.4 and earlier. This beta also
  includes patches to many issues shared with earlier versions, which
  will be updated in an upcoming minor release.
  Note that some known issues remain unfixed. Before reporting a bug
  in the beta, please check the Open Items page.</changelog>
  <changelog author="fweiss@suse.com" date="1471003200">- Update to 9.6beta4:
    9.6 Beta 4 includes the security fixes in the 2016-08-11
    Security Update, as well as the general bug fixes offered for
    stable versions. Additionally, it contains fixes for the
    following beta issues reported since the last beta:
  * Change minimum max_worker_processes from 1 to 0
  * Make array_to_tsvector() sort and de-duplicate the given
    strings
  * Fix ts_delete(tsvector, text[]) to cope with duplicate array
    entries
  * Fix hard to hit race condition in heapam's tuple locking code
  * Prevent "snapshot too old" from trying to return pruned TOAST
    tuples
  * Make INSERT-from-multiple-VALUES-rows handle targetlist
    indirection
  * Do not let PostmasterContext survive into background workers
  * Add missing casts in information schema
  * Fix assorted problems in recovery tests
  * Block interrupts during HandleParallelMessages()
  * Remove unused arguments from pg_replication_origin_xact_reset
    function
  * Correctly handle owned sequences with extensions
  * Many fixes for tsqueue.c
  * Eliminate a few more user-visible "cache lookup failed"
    errors
  * Teach parser to transform "x IS [NOT] DISTINCT FROM NULL" to
    a NullTest
  * Allow functions that return sets of tuples to return simple
    NULLs
  * Repair damage done by citext--1.1--1.2.sql
  * Correctly set up aggregate FILTER expression in
    partial-aggregation plans
    This beta also includes many documentation updates and
    improvements.
    Due to changes in system catalogs, a pg_upgrade or pg_dump and
    restore will be required for users migrating databases from
    earlier betas.
    Note that some known issues remain unfixed. Before reporting a
    bug in the beta, please check the Open Items page.</changelog>
  <changelog author="mrueckert@suse.de" date="1475409600">- update to 9.6.0 final
  For all the details see:
  https://www.postgresql.org/about/news/1703/
  https://wiki.postgresql.org/wiki/NewIn96
  https://www.postgresql.org/docs/current/static/release-9-6.html</changelog>
  <changelog author="max@suse.com" date="1476100800">- Build the libs in 9.6 rather then 9.5.</changelog>
  <changelog author="13ilya@gmail.com" date="1477828800">- update to 9.6.1
  This release contains a variety of fixes from 9.6.0.
  For information about new features in the 9.6 major release.
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-1.html</changelog>
  <changelog author="mrueckert@suse.de" date="1486641600">- upate to 9.6.2
  - Build corruption with CREATE INDEX CONCURRENTLY
  - Fixes for visibility and write-ahead-log stability
  For the full release notes, see:
  https://www.postgresql.org/docs/9.6/static/release-9-6-2.html</changelog>
  <changelog author="astieger@suse.com" date="1489579200">- fix tests with timezone 2017a
  postgresql-9.6.2-fix-timezone-tests.patch</changelog>
  <changelog author="max@suse.com" date="1494504000">- Update to version 9.6.3:
  * https://www.postgresql.org/docs/9.6/static/release-9-6-3.html
  * CVE-2017-7486, bsc#1037624: Restrict visibility of
    pg_user_mappings.umoptions, to protect passwords stored as
    user mapping options.
    !!! Manual action is needed to fix this in existing databases
    !!! See upstream release notes for details.
  * CVE-2017-7485, bsc#1038293: recognize PGREQUIRESSL variable
    again.
  * CVE-2017-7484, bsc#1037603: Prevent exposure of statistical
    information via leaky operators.
  * Obsoletes postgresql-9.6.2-fix-timezone-tests.patch
- Added "Requires: timezone" to Server Package (bsc#973660)
- Submit postgresql96 to SLE-12 (bsc#1038474, fate#321481).</changelog>
</package>
<package pkgid="8b46ea358c6e806e5925c5a66687a3b8ed5527365d0ed9c515e847e795c87846" name="psqlODBC" arch="src">
  <version epoch="0" ver="09.05.0400" rel="36.10"/>
  <changelog author="max@suse.de" date="1042113600">- psqlODBC (formerly postgresql-odbc) becomes a package of it's
  own, because it has been removed from the PostgreSQL
  core distribution and is now a separate project.
- New version: 7.2.5.</changelog>
  <changelog author="adrian@suse.de" date="1073822400">- add %run_ldconfig</changelog>
  <changelog author="max@suse.de" date="1074168000">- New version: 07.03.0200</changelog>
  <changelog author="max@suse.de" date="1076068800">- Added -fno-strict-aliasing to CFLAGS.</changelog>
  <changelog author="max@suse.de" date="1085486400">- Adapted a patch from Debian to fix a buffer overflow in ODBC driver
  (src/interfaces/odbc/): added parameter for target buffer size to
  make_string() to prevent buffer overflows and corrected all calls to
  it (http://bugs.debian.org/247306, SuSE Bugzilla #40714).
  With previous versions it was possible to crash (and possibly
  exploit) e. g. apache if a PHP script connected to a ODBC database
  with very long credential strings (DSN, username, password, etc.).</changelog>
  <changelog author="ro@suse.de" date="1100174400">- fixed file list</changelog>
  <changelog author="max@suse.de" date="1120219200">- New version: 08.00.0101
- Building with support for unixODBC.</changelog>
  <changelog author="max@suse.de" date="1120478400">- Re-added -fno-strict-aliasing .</changelog>
  <changelog author="max@suse.de" date="1137153600">- New version: 08.01.0102</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="max@suse.de" date="1166011200">- Avoid literal string comparison (#228225)
- New version: 08.02.0200
  - Added support for SSL and Kerberos
  - Reduce compiler warnings on x86_64
  - Many more improvements</changelog>
  <changelog author="max@suse.de" date="1185796800">- New version: 08.02.0400. Changes include:
  * Ditinguish the indicaitor and the octet_length field of APD
    clearly.
  * Handle @@IDENTITY more generally.
  * Take outer join into account so as to evaluate nullability.
  * Fix a bug about Keyset-driven cursors.
  * Change to use NULL indicator instead of the length buffer in
    SQLFetch.
  * Fix a bug which forgets unnamed plans too early especially when
    handling large objects.
  * Don't treat charcters whose value &gt;= 128 as alphanumeric in case
    of conversion of binary data to bytea.
  * Change ConfigDSN() so that it takes the options in Setup Dialog
    page 1 into account.
  * Simplify the memory management of statements'columns info so as to
    prevent memory leaks or a crash in parse_statement etc.
  * SQLTables("", SQL_ALL_SCHEMAS. "", ..) now returns a list of valid
    schemas.
  * SQLTables("", "", "", SQL_ALL_TABLE_TYPES) now returns a list of
    valid table types.
  * SQLGetInfo SQL_DATABASE_NAME now returns the database name.
  * Treat the tables in information_schema as system tables.
  * Correct the precision of SQL_NUMERIC_STRUCT.
  * Change the default max varchar size from 254 to 255.
  * Reset the fields information properly in case of SQLMoreResults.
  * Implement SQLDescribeParam() also in case of multi-command queries.
  * Handle dollar-quotes more properly.
  * Append DETAIL messages to GetDiag...() messages.
  * Remove WSAStartup() and WSACleanup() from DllMain.
  * Load libpq from the driver's folder.
  * Improve the implemetation of SQLSetPos(.., SQL_ADD/SQL_UPDATE)
    using the 8.2 new feature INSERT/UPDATE .. returning.</changelog>
  <changelog author="max@suse.de" date="1221134400">- New version: 08.03.0200. For details on the countless
  improvements and bug fixes, see:
  http://psqlodbc.projects.postgresql.org/release.html or
  /usr/share/doc/packages/psqlODBC/release.html</changelog>
  <changelog author="max@suse.de" date="1226491200">- Automate registering and unregistering the driver with unixODBC
  on installation and uninstallation (bnc#420850).</changelog>
  <changelog author="coolo@novell.com" date="1257249600">- updated patches to apply with fuzz=0</changelog>
  <changelog author="mhrusecky@suse.com" date="1366718400">- fix build on openSUSE &gt; 12.3 with new unixODBC</changelog>
  <changelog author="p.drouand@gmail.com" date="1426161600">- Update to version 09.03.0400
  * No short ChangeLog available; please read
    /usr/share/doc/packages/psqlODBC/release.html
- Remove depreciated AUTHORS section
- Remove psqlODBC-literal.patch; fixed on upstream release
- Update psqlodbc-08.03.0200-build.patch &gt; psqlodbc-build.patch
- Update project Url
- Use download Url as source
- Remove redundant %clean section</changelog>
  <changelog author="adam.majer@suse.de" date="1485518400">- Update to version 09.05.0400
  * Ignore the difference between CR LF, LF and CR line break when
    comparing expected and result output.
  * Fix the bug SQLGetDescFieldW or SQLColAttributeW mistakenly
    returns SQL_ERROR.
  * for complete list of changes, see
    /usr/share/doc/packages/psqlODBC/release.html</changelog>
</package>
<package pkgid="28be6cf139dda47f3b2a3be8e4948eedb2f9c518cf675e28e7fc53978a0171dd" name="psqlODBC" arch="x86_64">
  <version epoch="0" ver="09.05.0400" rel="36.10"/>
  <changelog author="max@suse.de" date="1137153600">- New version: 08.01.0102</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="max@suse.de" date="1166011200">- Avoid literal string comparison (#228225)
- New version: 08.02.0200
  - Added support for SSL and Kerberos
  - Reduce compiler warnings on x86_64
  - Many more improvements</changelog>
  <changelog author="max@suse.de" date="1185796800">- New version: 08.02.0400. Changes include:
  * Ditinguish the indicaitor and the octet_length field of APD
    clearly.
  * Handle @@IDENTITY more generally.
  * Take outer join into account so as to evaluate nullability.
  * Fix a bug about Keyset-driven cursors.
  * Change to use NULL indicator instead of the length buffer in
    SQLFetch.
  * Fix a bug which forgets unnamed plans too early especially when
    handling large objects.
  * Don't treat charcters whose value &gt;= 128 as alphanumeric in case
    of conversion of binary data to bytea.
  * Change ConfigDSN() so that it takes the options in Setup Dialog
    page 1 into account.
  * Simplify the memory management of statements'columns info so as to
    prevent memory leaks or a crash in parse_statement etc.
  * SQLTables("", SQL_ALL_SCHEMAS. "", ..) now returns a list of valid
    schemas.
  * SQLTables("", "", "", SQL_ALL_TABLE_TYPES) now returns a list of
    valid table types.
  * SQLGetInfo SQL_DATABASE_NAME now returns the database name.
  * Treat the tables in information_schema as system tables.
  * Correct the precision of SQL_NUMERIC_STRUCT.
  * Change the default max varchar size from 254 to 255.
  * Reset the fields information properly in case of SQLMoreResults.
  * Implement SQLDescribeParam() also in case of multi-command queries.
  * Handle dollar-quotes more properly.
  * Append DETAIL messages to GetDiag...() messages.
  * Remove WSAStartup() and WSACleanup() from DllMain.
  * Load libpq from the driver's folder.
  * Improve the implemetation of SQLSetPos(.., SQL_ADD/SQL_UPDATE)
    using the 8.2 new feature INSERT/UPDATE .. returning.</changelog>
  <changelog author="max@suse.de" date="1221134400">- New version: 08.03.0200. For details on the countless
  improvements and bug fixes, see:
  http://psqlodbc.projects.postgresql.org/release.html or
  /usr/share/doc/packages/psqlODBC/release.html</changelog>
  <changelog author="max@suse.de" date="1226491200">- Automate registering and unregistering the driver with unixODBC
  on installation and uninstallation (bnc#420850).</changelog>
  <changelog author="coolo@novell.com" date="1257249600">- updated patches to apply with fuzz=0</changelog>
  <changelog author="mhrusecky@suse.com" date="1366718400">- fix build on openSUSE &gt; 12.3 with new unixODBC</changelog>
  <changelog author="p.drouand@gmail.com" date="1426161600">- Update to version 09.03.0400
  * No short ChangeLog available; please read
    /usr/share/doc/packages/psqlODBC/release.html
- Remove depreciated AUTHORS section
- Remove psqlODBC-literal.patch; fixed on upstream release
- Update psqlodbc-08.03.0200-build.patch &gt; psqlodbc-build.patch
- Update project Url
- Use download Url as source
- Remove redundant %clean section</changelog>
  <changelog author="adam.majer@suse.de" date="1485518400">- Update to version 09.05.0400
  * Ignore the difference between CR LF, LF and CR line break when
    comparing expected and result output.
  * Fix the bug SQLGetDescFieldW or SQLColAttributeW mistakenly
    returns SQL_ERROR.
  * for complete list of changes, see
    /usr/share/doc/packages/psqlODBC/release.html</changelog>
</package>
<package pkgid="cde4947cb3e2f8441248196f2cffcd12bdc157afdba5bf1efc0a3e75455b3dc9" name="psqlODBC-debuginfo" arch="x86_64">
  <version epoch="0" ver="09.05.0400" rel="36.10"/>
  <changelog author="max@suse.de" date="1042113600">- psqlODBC (formerly postgresql-odbc) becomes a package of it's
  own, because it has been removed from the PostgreSQL
  core distribution and is now a separate project.
- New version: 7.2.5.</changelog>
  <changelog author="adrian@suse.de" date="1073822400">- add %run_ldconfig</changelog>
  <changelog author="max@suse.de" date="1074168000">- New version: 07.03.0200</changelog>
  <changelog author="max@suse.de" date="1076068800">- Added -fno-strict-aliasing to CFLAGS.</changelog>
  <changelog author="max@suse.de" date="1085486400">- Adapted a patch from Debian to fix a buffer overflow in ODBC driver
  (src/interfaces/odbc/): added parameter for target buffer size to
  make_string() to prevent buffer overflows and corrected all calls to
  it (http://bugs.debian.org/247306, SuSE Bugzilla #40714).
  With previous versions it was possible to crash (and possibly
  exploit) e. g. apache if a PHP script connected to a ODBC database
  with very long credential strings (DSN, username, password, etc.).</changelog>
  <changelog author="ro@suse.de" date="1100174400">- fixed file list</changelog>
  <changelog author="max@suse.de" date="1120219200">- New version: 08.00.0101
- Building with support for unixODBC.</changelog>
  <changelog author="max@suse.de" date="1120478400">- Re-added -fno-strict-aliasing .</changelog>
  <changelog author="max@suse.de" date="1137153600">- New version: 08.01.0102</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="max@suse.de" date="1166011200">- Avoid literal string comparison (#228225)
- New version: 08.02.0200
  - Added support for SSL and Kerberos
  - Reduce compiler warnings on x86_64
  - Many more improvements</changelog>
  <changelog author="max@suse.de" date="1185796800">- New version: 08.02.0400. Changes include:
  * Ditinguish the indicaitor and the octet_length field of APD
    clearly.
  * Handle @@IDENTITY more generally.
  * Take outer join into account so as to evaluate nullability.
  * Fix a bug about Keyset-driven cursors.
  * Change to use NULL indicator instead of the length buffer in
    SQLFetch.
  * Fix a bug which forgets unnamed plans too early especially when
    handling large objects.
  * Don't treat charcters whose value &gt;= 128 as alphanumeric in case
    of conversion of binary data to bytea.
  * Change ConfigDSN() so that it takes the options in Setup Dialog
    page 1 into account.
  * Simplify the memory management of statements'columns info so as to
    prevent memory leaks or a crash in parse_statement etc.
  * SQLTables("", SQL_ALL_SCHEMAS. "", ..) now returns a list of valid
    schemas.
  * SQLTables("", "", "", SQL_ALL_TABLE_TYPES) now returns a list of
    valid table types.
  * SQLGetInfo SQL_DATABASE_NAME now returns the database name.
  * Treat the tables in information_schema as system tables.
  * Correct the precision of SQL_NUMERIC_STRUCT.
  * Change the default max varchar size from 254 to 255.
  * Reset the fields information properly in case of SQLMoreResults.
  * Implement SQLDescribeParam() also in case of multi-command queries.
  * Handle dollar-quotes more properly.
  * Append DETAIL messages to GetDiag...() messages.
  * Remove WSAStartup() and WSACleanup() from DllMain.
  * Load libpq from the driver's folder.
  * Improve the implemetation of SQLSetPos(.., SQL_ADD/SQL_UPDATE)
    using the 8.2 new feature INSERT/UPDATE .. returning.</changelog>
  <changelog author="max@suse.de" date="1221134400">- New version: 08.03.0200. For details on the countless
  improvements and bug fixes, see:
  http://psqlodbc.projects.postgresql.org/release.html or
  /usr/share/doc/packages/psqlODBC/release.html</changelog>
  <changelog author="max@suse.de" date="1226491200">- Automate registering and unregistering the driver with unixODBC
  on installation and uninstallation (bnc#420850).</changelog>
  <changelog author="coolo@novell.com" date="1257249600">- updated patches to apply with fuzz=0</changelog>
  <changelog author="mhrusecky@suse.com" date="1366718400">- fix build on openSUSE &gt; 12.3 with new unixODBC</changelog>
  <changelog author="p.drouand@gmail.com" date="1426161600">- Update to version 09.03.0400
  * No short ChangeLog available; please read
    /usr/share/doc/packages/psqlODBC/release.html
- Remove depreciated AUTHORS section
- Remove psqlODBC-literal.patch; fixed on upstream release
- Update psqlodbc-08.03.0200-build.patch &gt; psqlodbc-build.patch
- Update project Url
- Use download Url as source
- Remove redundant %clean section</changelog>
  <changelog author="adam.majer@suse.de" date="1485518400">- Update to version 09.05.0400
  * Ignore the difference between CR LF, LF and CR line break when
    comparing expected and result output.
  * Fix the bug SQLGetDescFieldW or SQLColAttributeW mistakenly
    returns SQL_ERROR.
  * for complete list of changes, see
    /usr/share/doc/packages/psqlODBC/release.html</changelog>
</package>
<package pkgid="50cf71b37d8487e5918f364ee986a8a28d4b9ea8f5b9ab5de4c2fc82144078d5" name="psqlODBC-debugsource" arch="x86_64">
  <version epoch="0" ver="09.05.0400" rel="36.10"/>
  <changelog author="max@suse.de" date="1137153600">- New version: 08.01.0102</changelog>
  <changelog author="mls@suse.de" date="1138190400">- converted neededforbuild to BuildRequires</changelog>
  <changelog author="max@suse.de" date="1166011200">- Avoid literal string comparison (#228225)
- New version: 08.02.0200
  - Added support for SSL and Kerberos
  - Reduce compiler warnings on x86_64
  - Many more improvements</changelog>
  <changelog author="max@suse.de" date="1185796800">- New version: 08.02.0400. Changes include:
  * Ditinguish the indicaitor and the octet_length field of APD
    clearly.
  * Handle @@IDENTITY more generally.
  * Take outer join into account so as to evaluate nullability.
  * Fix a bug about Keyset-driven cursors.
  * Change to use NULL indicator instead of the length buffer in
    SQLFetch.
  * Fix a bug which forgets unnamed plans too early especially when
    handling large objects.
  * Don't treat charcters whose value &gt;= 128 as alphanumeric in case
    of conversion of binary data to bytea.
  * Change ConfigDSN() so that it takes the options in Setup Dialog
    page 1 into account.
  * Simplify the memory management of statements'columns info so as to
    prevent memory leaks or a crash in parse_statement etc.
  * SQLTables("", SQL_ALL_SCHEMAS. "", ..) now returns a list of valid
    schemas.
  * SQLTables("", "", "", SQL_ALL_TABLE_TYPES) now returns a list of
    valid table types.
  * SQLGetInfo SQL_DATABASE_NAME now returns the database name.
  * Treat the tables in information_schema as system tables.
  * Correct the precision of SQL_NUMERIC_STRUCT.
  * Change the default max varchar size from 254 to 255.
  * Reset the fields information properly in case of SQLMoreResults.
  * Implement SQLDescribeParam() also in case of multi-command queries.
  * Handle dollar-quotes more properly.
  * Append DETAIL messages to GetDiag...() messages.
  * Remove WSAStartup() and WSACleanup() from DllMain.
  * Load libpq from the driver's folder.
  * Improve the implemetation of SQLSetPos(.., SQL_ADD/SQL_UPDATE)
    using the 8.2 new feature INSERT/UPDATE .. returning.</changelog>
  <changelog author="max@suse.de" date="1221134400">- New version: 08.03.0200. For details on the countless
  improvements and bug fixes, see:
  http://psqlodbc.projects.postgresql.org/release.html or
  /usr/share/doc/packages/psqlODBC/release.html</changelog>
  <changelog author="max@suse.de" date="1226491200">- Automate registering and unregistering the driver with unixODBC
  on installation and uninstallation (bnc#420850).</changelog>
  <changelog author="coolo@novell.com" date="1257249600">- updated patches to apply with fuzz=0</changelog>
  <changelog author="mhrusecky@suse.com" date="1366718400">- fix build on openSUSE &gt; 12.3 with new unixODBC</changelog>
  <changelog author="p.drouand@gmail.com" date="1426161600">- Update to version 09.03.0400
  * No short ChangeLog available; please read
    /usr/share/doc/packages/psqlODBC/release.html
- Remove depreciated AUTHORS section
- Remove psqlODBC-literal.patch; fixed on upstream release
- Update psqlodbc-08.03.0200-build.patch &gt; psqlodbc-build.patch
- Update project Url
- Use download Url as source
- Remove redundant %clean section</changelog>
  <changelog author="adam.majer@suse.de" date="1485518400">- Update to version 09.05.0400
  * Ignore the difference between CR LF, LF and CR line break when
    comparing expected and result output.
  * Fix the bug SQLGetDescFieldW or SQLColAttributeW mistakenly
    returns SQL_ERROR.
  * for complete list of changes, see
    /usr/share/doc/packages/psqlODBC/release.html</changelog>
</package>
<package pkgid="3854cfad47c8d5f7f2b83b553ade9bde06bf753d67b9cd4c872f23d3f6935756" name="python-argcomplete" arch="noarch">
  <version epoch="0" ver="1.0.0" rel="16.1"/>
  <changelog author="darin@darins.net" date="1366977600">- Initial packaging</changelog>
  <changelog author="darin@darins.net" date="1366977601">- add files in _bindir
- add python-distribute</changelog>
  <changelog author="darin@darins.net" date="1367236800">- fixed license, set noarch for build</changelog>
  <changelog author="speilicke@suse.com" date="1367496000">- Fix SLE builds
- Add LICENSE.rst and README.rst
- Run testsuite</changelog>
  <changelog author="speilicke@suse.com" date="1382616000">- Require python-setuptools instead of distribute (upstreams merged)</changelog>
  <changelog author="speilicke@suse.com" date="1384776000">- Update to version 0.6.3:
  + No changelog</changelog>
  <changelog author="speilicke@suse.com" date="1389960000">- Update to version 0.6.7:
  + Upstream provides no changelog
- Don't install testsuite globally</changelog>
  <changelog author="benoit.monin@gmx.fr" date="1429444800">- update to 0.8.7:
  * register-python-argcomplete: add option to avoid default
    readline completion. Thanks to @drmalex07 (pull request #99).
- additional changes from 0.8.6:
  * Expand tilde in script name, allowing argcomplete to work
    when invoking scripts from one's home directory. Thanks to
    @VorpalBlade (Issue 104).
- additional changes from 0.8.5:
  * Fix issues related to using argcomplete in a REPL
    environement.
  * New helper method for custom completion display.
  * Expand test suite; formatting cleanup.
- additional changes from 0.8.4:
  * Fix issue related to using argcomplete in a REPL
    environement. Thanks to @wapiflapi (pull request #91).
- additional changes from 0.8.3:
  * Fix multiple issues related to using argcomplete in a REPL
    environement. Thanks to @wapiflapi (pull request #90).
- additional changes from 0.8.2:
  * Don't strip colon prefix in completion results if
    COMP_WORDBREAKS does not contain a colon. Thanks to @berezv
    (pull request #88).
- additional changes from 0.8.1:
  * Use complete --nospace to avoid issues with directory
    completion.
- additional changes from 0.8.0:
  * Refactor main body of code into a class to enable
    subclassing and overriding of functionality (Issue #78).
- additional changes from 0.7.1:
  * New keyword option "argcomplete.autocomplete(validator=...)"
    to supply a custom validator or bypass default validation.
    Thanks to @thijsdezoete (Issue #77).
  * Document debug options.
- additional changes from 0.7.0:
  * New keyword option "argcomplete.autocomplete(exclude=[...])"
    to suppress options (Issue #74).
  * More speedups to code path for global completion hook negative
    result.
- additional changes from 0.6.9:
  * Fix handling of development mode script wrappers. Thanks to
    @jmlopez-rod and @dcosson (Issue #69).
  * Speed up code path for global completion hook negative
    result by loading pkg_resources on demand.
- additional changes from 0.6.8:
  * Begin tracking changes in changelog.
  * Add completion support for PBR installed scripts (PR #71).
  * Detect easy-install shims with shebang lines that contain
    Py instead of py (Issue #69).</changelog>
  <changelog author="mimi.vx@gmail.com" date="1449921600">- update to 1.0.0
  * Don't print args with suppressed help by default; add
  argcomplete.autocomplete(print_suppressed=True) to control this behavior
  * Fix always_complete_options=False support.
  * Correct doc filename in setup.cfg
  * Make context managers exception-safe.
  * Fix issue with non-string choices for arguments.
  * Improve non-ascii argparse argument support on Python 2.7.</changelog>
  <changelog author="achim.herwig@wodca.de" date="1478088000">- ported back from python3 package including
  introduced update-alternatives to coexist with corresponding python3 package</changelog>
</package>
<package pkgid="db9ec6efa7182abcdf250acde378672124aa1ae3f217b32eb5bc3917c8fef928" name="python-argcomplete" arch="src">
  <version epoch="0" ver="1.0.0" rel="16.1"/>
  <changelog author="darin@darins.net" date="1366977600">- Initial packaging</changelog>
  <changelog author="darin@darins.net" date="1366977601">- add files in _bindir
- add python-distribute</changelog>
  <changelog author="darin@darins.net" date="1367236800">- fixed license, set noarch for build</changelog>
  <changelog author="speilicke@suse.com" date="1367496000">- Fix SLE builds
- Add LICENSE.rst and README.rst
- Run testsuite</changelog>
  <changelog author="speilicke@suse.com" date="1382616000">- Require python-setuptools instead of distribute (upstreams merged)</changelog>
  <changelog author="speilicke@suse.com" date="1384776000">- Update to version 0.6.3:
  + No changelog</changelog>
  <changelog author="speilicke@suse.com" date="1389960000">- Update to version 0.6.7:
  + Upstream provides no changelog
- Don't install testsuite globally</changelog>
  <changelog author="benoit.monin@gmx.fr" date="1429444800">- update to 0.8.7:
  * register-python-argcomplete: add option to avoid default
    readline completion. Thanks to @drmalex07 (pull request #99).
- additional changes from 0.8.6:
  * Expand tilde in script name, allowing argcomplete to work
    when invoking scripts from one's home directory. Thanks to
    @VorpalBlade (Issue 104).
- additional changes from 0.8.5:
  * Fix issues related to using argcomplete in a REPL
    environement.
  * New helper method for custom completion display.
  * Expand test suite; formatting cleanup.
- additional changes from 0.8.4:
  * Fix issue related to using argcomplete in a REPL
    environement. Thanks to @wapiflapi (pull request #91).
- additional changes from 0.8.3:
  * Fix multiple issues related to using argcomplete in a REPL
    environement. Thanks to @wapiflapi (pull request #90).
- additional changes from 0.8.2:
  * Don't strip colon prefix in completion results if
    COMP_WORDBREAKS does not contain a colon. Thanks to @berezv
    (pull request #88).
- additional changes from 0.8.1:
  * Use complete --nospace to avoid issues with directory
    completion.
- additional changes from 0.8.0:
  * Refactor main body of code into a class to enable
    subclassing and overriding of functionality (Issue #78).
- additional changes from 0.7.1:
  * New keyword option "argcomplete.autocomplete(validator=...)"
    to supply a custom validator or bypass default validation.
    Thanks to @thijsdezoete (Issue #77).
  * Document debug options.
- additional changes from 0.7.0:
  * New keyword option "argcomplete.autocomplete(exclude=[...])"
    to suppress options (Issue #74).
  * More speedups to code path for global completion hook negative
    result.
- additional changes from 0.6.9:
  * Fix handling of development mode script wrappers. Thanks to
    @jmlopez-rod and @dcosson (Issue #69).
  * Speed up code path for global completion hook negative
    result by loading pkg_resources on demand.
- additional changes from 0.6.8:
  * Begin tracking changes in changelog.
  * Add completion support for PBR installed scripts (PR #71).
  * Detect easy-install shims with shebang lines that contain
    Py instead of py (Issue #69).</changelog>
  <changelog author="mimi.vx@gmail.com" date="1449921600">- update to 1.0.0
  * Don't print args with suppressed help by default; add
  argcomplete.autocomplete(print_suppressed=True) to control this behavior
  * Fix always_complete_options=False support.
  * Correct doc filename in setup.cfg
  * Make context managers exception-safe.
  * Fix issue with non-string choices for arguments.
  * Improve non-ascii argparse argument support on Python 2.7.</changelog>
  <changelog author="achim.herwig@wodca.de" date="1478088000">- ported back from python3 package including
  introduced update-alternatives to coexist with corresponding python3 package</changelog>
</package>
<package pkgid="0c4d2cb665ae0cc39dbfc18e8e4a701f7cb0d303bcc192992bbf743b2f01c5c6" name="python-argh" arch="noarch">
  <version epoch="0" ver="0.26.1" rel="21.1"/>
  <changelog author="saschpe@suse.de" date="1328011200">- Initial version</changelog>
  <changelog author="os-dev@jacraig.com" date="1338984000">- Update to version 0.15.1:
  + Upstream provides no changelog</changelog>
  <changelog author="saschpe@suse.de" date="1353672000">- Update to version 0.17.2:
  + Upstream provides no changelog</changelog>
  <changelog author="darin@darins.net" date="1362657600">- Update to verios 0.23.0
  + Upstream provides no changelog</changelog>
  <changelog author="p.drouand@gmail.com" date="1380110400">- Update to version 0.23.3
  + No changelog available</changelog>
  <changelog author="speilicke@suse.com" date="1382616000">- Require python-setuptools instead of distribute (upstreams merged)</changelog>
  <changelog author="benoit.monin@gmx.fr" date="1429444800">- update to version 0.26.1
  * no changelog available
- update project URL
- package README.rst instead of README</changelog>
</package>
<package pkgid="1b6dbebf0142a50e6774aa95860b5363bd8d23cc0f608954059c05defeb9f25c" name="python-argh" arch="src">
  <version epoch="0" ver="0.26.1" rel="21.1"/>
  <changelog author="saschpe@suse.de" date="1328011200">- Initial version</changelog>
  <changelog author="os-dev@jacraig.com" date="1338984000">- Update to version 0.15.1:
  + Upstream provides no changelog</changelog>
  <changelog author="saschpe@suse.de" date="1353672000">- Update to version 0.17.2:
  + Upstream provides no changelog</changelog>
  <changelog author="darin@darins.net" date="1362657600">- Update to verios 0.23.0
  + Upstream provides no changelog</changelog>
  <changelog author="p.drouand@gmail.com" date="1380110400">- Update to version 0.23.3
  + No changelog available</changelog>
  <changelog author="speilicke@suse.com" date="1382616000">- Require python-setuptools instead of distribute (upstreams merged)</changelog>
  <changelog author="benoit.monin@gmx.fr" date="1429444800">- update to version 0.26.1
  * no changelog available
- update project URL
- package README.rst instead of README</changelog>
</package>
<package pkgid="a0f38c37a505b292013d17d9dedbd12b01c73e1e76d9e7b497469f024a74427e" name="python-psycopg2" arch="src">
  <version epoch="0" ver="2.6.2" rel="3.17"/>
  <changelog author="jfunk@funktronics.ca" date="1250596800">- Update to 2.0.12:
  * psycopg/lobject_int.c: fixed problem with writing large data using
    lo_write: apparently the large objects code does not like non-blocking
    connections.
  * setup.py: fixed version detection for PostgreSQL rc, as
    suggested by Sok Ann Yap.
  * ZPsycopgDA/db.py: applied serialization error retry from Brian
    Sutherland.
  * Implemented connection.reset() method to reset the connection to
    well-know default parameters. This is much faster than closing and
    reopening the connection. (Suggested by a bug report by Glenn
    Maynard.)
  * psycopg/cursor_type.c: unified size macro definitions in COPY TO
    and COPY FROM operations: now the buffer for column names is 8192
    bytes that should be enough even for very large tables.
  * Applied patch from Robert Munro to fix version check
    in ZPsycopgDA.
- Release 2.0.11:
  * lib/extras.py: fixed crash in fetchone() when prefetching using
    a RealDictCursor.
  * psycopg/cursor_ext.c: now raise correct exception when fetching
    using a custom row factory results in an error.
  * lib/extras.py: applied DictRow "diet" patch from Marko Kreen.
  * setup.py: applied patch from Elvis Pranskevichus to make
    PostgreSQL version detection more robust.</changelog>
  <changelog author="jnelson-suse@jamponi.net" date="1251201600">- Add --optimize=2 to build .pyo files, correct License and Url</changelog>
  <changelog author="termim@gmail.com" date="1288180800">- Update to 2.2.2:
    Bux fixes:
  * the call to logging.basicConfig() in pool.py has been dropped:
    it was messing with some projects using logging (and a library
    should not initialize the logging system anyway.)
  * psycopg now correctly handles time zones with seconds in the
    UTC offset. The old register_tstz_w_secs() function is deprecated
    and will raise a warning if called.
  * Exceptions raised by the column iterator are propagated.
  * Exceptions raised by executemany() interators are propagated.</changelog>
  <changelog author="elchevive@opensuse.org" date="1293451200">- Update to version 2.3.2</changelog>
  <changelog author="saschpe@suse.de" date="1298894400">- Spec file changes:
  * Added LICENSE and NEWS files
  * Added ZPL license to preamble (psycopg2 is dual-licensed)
  * Use upstream description
  * Fixed SLE build errors
  * Repacked tarball to bzip2
- Update to version 2.4
  * Added support for Python 3.1 and 3.2. The conversion has also
    brought several improvements:
  * Improvements to the named cusors and data handling
  * Fixed adaptation of None in composite types (ticket #26). Bug
    report by Karsten Hilbert.
  * Fixed several reference leaks in less common code paths.
  * Fixed segfault when a large object is closed and its connection no
    more available.
  * Added missing icon to ZPsycopgDA package, not available in Zope
    2.12.9 (ticket #30). Bug report and patch by Pumukel.
  * Fixed conversion of negative infinity (ticket #40). Bug report and
    patch by Marti Raudsepp.</changelog>
  <changelog author="saschpe@suse.de" date="1316606400">- Update to version 2.4.2:
  * connection.h: added codec attribute to avoid repeated codec name
    lookups during unicode query/params manipulations.
  * setup.py: bumped to version 2.3.2.dev0
  * psycopg/connection_int.c: applied patch from Marti Raudsepp to close
    ticket #24. Fixed segfault in connection when DateStyle not available
    (e.g.  pgbouncer appars not passing it to the client)
  * psycopg/utils.c: Added psycopg_strdup function.
  - See ChangeLog for more...
- Don't package testsuite
- Fix non-executable script rpmlint warning</changelog>
  <changelog author="jfunk@funktronics.ca" date="1326369600">- Update to 2.4.4:
  * register_composite() also works with the types implicitly defined after a
    table row, not only with the ones created by CREATE TYPE.
  * Values for the isolation level symbolic constants restored to what they
    were before release 2.4.2 to avoid breaking apps using the values instead
    of the constants.
  * Named DictCursor/RealDictCursor honour itersize (ticket #80).
  * Fixed rollback on error on Zope (ticket #73).
  * Raise DatabaseError instead of Error with empty libpq errors, consistently
    with other disconnection-related errors: regression introduced in release
    2.4.1 (ticket #82).
- Version 2.4.3:
  * connect() supports all the keyword arguments supported by the database
  * Added new_array_type() function for easy creation of array typecasters.
  * Added support for arrays of hstores and composite types (ticket #66).
  * Fixed segfault in case of transaction started with connection lost (and
    possibly other events).
  * Fixed adaptation of Decimal type in sub-interpreters, such as in certain
    mod_wsgi configurations (ticket #52).
  * Rollback connections in transaction or in error before putting them back
    into a pool. Also discard broken connections (ticket #62).
  * Lazy import of the slow uuid module, thanks to Marko Kreen.
  * Fixed NamedTupleCursor.executemany() (ticket #65).
  * Fixed --static-libpq setup option (ticket #64).
  * Fixed interaction between RealDictCursor and named cursors (ticket #67).
  * Dropped limit on the columns length in COPY operations (ticket #68).
  * Fixed reference leak with arguments referenced more than once in queries
    (ticket #81).
  * Fixed typecasting of arrays containing consecutive backslashes.
  * errorcodes map updated to PostgreSQL 9.1.</changelog>
  <changelog author="coolo@suse.com" date="1329134400">- patch license to follow spdx.org standard</changelog>
  <changelog author="saschpe@gmx.de" date="1331553600">- Simplify macro usage
- Remove outdated SUSE version checks</changelog>
  <changelog author="saschpe@suse.de" date="1332849600">- Can't hurt to suggest postgresql-server</changelog>
  <changelog author="jfunk@funktronics.ca" date="1333713600">- Update to 2.4.5:
  * The close() methods on connections and cursors don't raise exceptions
    if called on already closed objects.
  * Fixed fetchmany() with no argument in cursor subclasses
    (ticket #84).
  * Use lo_creat() instead of lo_create() when possible for better
    interaction with pgpool-II (ticket #88).
  * Error and its subclasses are picklable, useful for multiprocessing
    interaction (ticket #90).
  * Better efficiency and formatting of timezone offset objects thanks
    to Menno Smits (tickets #94, #95).
  * Fixed 'rownumber' during iteration on cursor subclasses.
    Regression introduced in 2.4.4 (ticket #100).
  * Added support for 'inet' arrays.
  * Fixed 'commit()' concurrency problem (ticket #103).
  * Codebase cleaned up using the GCC Python plugin's static analysis
    tool, which has revealed several unchecked return values, possible
    NULL dereferences, reference counting problems. Many thanks to David
    Malcolm for the useful tool and the assistance provided using it.</changelog>
  <changelog author="highwaystar.ru@gmail.com" date="1337947200">- python3 package added
- minor spec improvement</changelog>
  <changelog author="cfarrell@suse.com" date="1337947201">- license update: LGPL-3.0+ and (LGPL-3.0+ or ZPL-2.0) and
  SUSE-GPL-2.0-with-openssl-exception
  See the COPYING file. There are GPL-2.0+ (with openssl linking exceptions
  for pgsql) in the package. Also, the ZPL option is only available for one
  particular subdirectory in the package</changelog>
  <changelog author="jfunk@funktronics.ca" date="1366113600">- Update to 2.5:
  - Added JSON adaptation.
  - Added support for PostgreSQL 9.2 range types.
  - `connection` and `cursor` objects can be used in ``with`` statements as
    context managers as specified by recent DBAPI extension.
  - Added `psycopg2.extensions.Diagnostics` object to get extended info from
    a database error.  Many thanks to Matthew Woodcraft for the implementation
    (ticket #149).
  - Added `connection.cursor_factory` attribute to customize the default
    object returned by `connection.cursor()`.
  - Added support for backward scrollable cursors. Thanks to Jon Nelson for
    the initial patch (ticket #108).
  - Added a simple way to customize casting of composite types into Python
    objects other than namedtuples. Many thanks to Ronan Dunklau and Tobias
    Oberstein for the feature development.
  - `connection.reset()` implemented using `DISCARD ALL` on server versions
    supporting it.
  - Properly cleanup memory of broken connections (ticket #148).
  - Fixed bad interaction of ``setup.py`` with other dependencies in
    Distribute projects on Python 3 (ticket #153).
  - Added support for Python 3.3.
  - Dropped support for Python 2.4. Please use Psycopg 2.4.x if you need it.
  - `psycopg2.errorcodes` map updated to PostgreSQL 9.2.
  - Dropped Zope adapter from source repository. ZPsycopgDA now has its own
    project at &lt;http://github.com/psycopg/ZPsycopgDA&gt;.
- Changes from 2.4.6:
  - Fixed 'cursor()' arguments propagation in connection subclasses and
    overriding of the 'cursor_factory' argument. Thanks to Corry Haines for
    the report and the initial patch (ticket #105).
  - Dropped GIL release during string adaptation around a function call
    invoking a Python API function, which could cause interpreter crash.
    Thanks to Manu Cupcic for the report (ticket #110).
  - Close a green connection if there is an error in the callback. Maybe a
    harsh solution but it leaves the program responsive (ticket #113).
  - 'register_hstore()', 'register_composite()', 'tpc_recover()' work with
    RealDictConnection and Cursor (ticket #114).
  - Fixed broken pool for Zope and connections re-init across ZSQL methods in
    the same request (tickets #123, #125, #142).
  - connect() raises an exception instead of swallowing keyword arguments when
    a connection string is specified as well (ticket #131).
  - Discard any result produced by 'executemany()' (ticket #133).
  - Fixed pickling of FixedOffsetTimezone objects (ticket #135).
  - Release the GIL around PQgetResult calls after COPY (ticket #140).
  - Fixed empty strings handling in composite caster (ticket #141).
  - Fixed pickling of DictRow and RealDictRow objects.</changelog>
  <changelog author="dmueller@suse.com" date="1372161600">- update to 2.5.1:
  - Fixed build on Solaris 10 and 11 where the round() function is already
  declared (:ticket:`#146`).
  - Fixed comparison of `Range` with non-range objects (:ticket:`#164`).
  Thanks to Chris Withers for the patch.
  - Fixed double-free on connection dealloc (:ticket:`#166`). Thanks to
  Gangadharan S.A. for the report and fix suggestion.</changelog>
  <changelog author="dmueller@suse.com" date="1389614400">- update to 2.5.2:
  - Fixed segfault pickling the exception raised on connection error
  - Meaningful connection errors report a meaningful message
  - Manually creating `lobject` with the wrong parameter doesn't segfault</changelog>
  <changelog author="tbechtold@suse.com" date="1424779200">- update to version 2.6:
  - Added support for large objects larger than 2GB. Many thanks to Blake Rouse
    and the MAAS Team for the feature development.
  - Python `time` objects with a tzinfo specified and PostgreSQL :sql:`timetz`
    data are converted into each other (:ticket:`#272`).
  - Json apapter's `!str()` returns the adapted content instead of the `!repr()`
    (:ticket:`#191`).
  - Named cursors used as context manager don't swallow the exception on exit
    (:ticket:`#262`).
  - `cursor.description` can be pickled (:ticket:`#265`).
  - Propagate read error messages in COPY FROM (:ticket:`#270`).
  - PostgreSQL time 24:00 is converted to Python 00:00 (:ticket:`#278`).
  - Added :sql:`jsonb` support for PostgreSQL 9.4 (:ticket:`#226`).
  - Fixed segfault if COPY statements are passed to `~cursor.execute()` instead
    of using the proper methods (:ticket:`#219`).
  - Force conversion of pool arguments to integer to avoid potentially unbounded
    pools (:ticket:`#220`).
  - Cursors :sql:`WITH HOLD` don't begin a new transaction upon move/fetch/close
    (:ticket:`#228`).
  - Cursors :sql:`WITH HOLD` can be used in autocommit (:ticket:`#229`).
  - `~cursor.callproc()` doesn't silently ignore an argument without a length.
  - Fixed memory leak with large objects (:ticket:`#256`).
  - Make sure the internal ``_psycopg.so`` module can be imported stand-alone (to
    allow modules juggling such as the one described in :ticket:`#201`).
  - Work around `pip issue #1630 &lt;https://github.com/pypa/pip/issues/1630&gt;`__
    making installation via ``pip -e git+url`` impossible (:ticket:`#18`).
  - Copy operations correctly set the `cursor.rowcount` attribute
    (:ticket:`#180`).
  - It is now possible to call `get_transaction_status()` on closed connections.
  - Fixed unsafe access to object names causing assertion failures in
    Python 3 debug builds (:ticket:`#188`).
  - Mark the connection closed if found broken on `poll()` (from :ticket:`#192`
    discussion)
  - Fixed handling of dsn and closed attributes in connection subclasses
    failing to connect (from :ticket:`#192` discussion).
  - Added arbitrary but stable order to `Range` objects, thanks to
    Chris Withers (:ticket:`#193`).
  - Avoid blocking async connections on connect (:ticket:`#194`). Thanks to
    Adam Petrovich for the bug report and diagnosis.
  - Don't segfault using poorly defined cursor subclasses which forgot to call
    the superclass init (:ticket:`#195`).
  - Mark the connection closed when a Socket connection is broken, as it
    happens for TCP connections instead (:ticket:`#196`).
  - Fixed overflow opening a lobject with an oid not fitting in a signed int
    (:ticket:`#203`).
  - Fixed handling of explicit default ``cursor_factory=None`` in
    `connection.cursor()` (:ticket:`#210`).
  - Fixed possible segfault in named cursors creation.
  - Fixed debug build on Windows, thanks to James Emerton.
- Add python-Sphinx as BuilrRequires to build documenation. Also adjust
  the build process for html docs.</changelog>
  <changelog author="bwiedemann@suse.com" date="1457524800">- use the year from source gzip header instead of current one
  to make reproducible rpms</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- disable docs on SLE due to lack of python-Sphinx</changelog>
  <changelog author="dmueller@suse.com" date="1479124800">- update to 2.6.2:
  * Fixed inconsistent state in externally closed connections (tickets #263, #311, #443).
  * Report the server response status on errors (such as ticket #281).
  * Raise NotSupportedError on unhandled server response status (ticket #352).
  * Allow overriding string adapter encoding with no connection (ticket #331).
  * The wait_select callback allows interrupting a long-running query in an interactive shell using Ctrl-C (ticket #333).
  * Fixed PersistentConnectionPool on Python 3 (ticket #348).
  * Fixed segfault on repr() of an uninitialized connection (ticket #361).
  * Allow adapting bytes using QuotedString on Python 3 (ticket #365).
  * Added support for setuptools/wheel (ticket #370).
  * Fix build on Windows with Python 3.5, VS 2015 (ticket #380).
  * Fixed errorcodes.lookup initialization thread-safety (ticket #382).
  * Fixed read() exception propagation in copy_from (ticket #412).
  * Fixed possible NULL TZ decref (ticket #424).
  * errorcodes map updated to PostgreSQL 9.5.
  * Lists consisting of only None are escaped correctly (ticket #285).
  * Fixed deadlock in multithread programs using OpenSSL (ticket #290).
  * Correctly unlock the connection after error in flush (ticket #294).
  * Fixed MinTimeLoggingCursor.callproc() (ticket #309).
  * Added support for MSVC 2015 compiler (ticket #350).</changelog>
</package>
<package pkgid="eb93e2654e5bf03b689f424b97e39dcff617949466395424c1dda920403b10d6" name="python-psycopg2" arch="x86_64">
  <version epoch="0" ver="2.6.2" rel="3.17"/>
  <changelog author="jfunk@funktronics.ca" date="1250596800">- Update to 2.0.12:
  * psycopg/lobject_int.c: fixed problem with writing large data using
    lo_write: apparently the large objects code does not like non-blocking
    connections.
  * setup.py: fixed version detection for PostgreSQL rc, as
    suggested by Sok Ann Yap.
  * ZPsycopgDA/db.py: applied serialization error retry from Brian
    Sutherland.
  * Implemented connection.reset() method to reset the connection to
    well-know default parameters. This is much faster than closing and
    reopening the connection. (Suggested by a bug report by Glenn
    Maynard.)
  * psycopg/cursor_type.c: unified size macro definitions in COPY TO
    and COPY FROM operations: now the buffer for column names is 8192
    bytes that should be enough even for very large tables.
  * Applied patch from Robert Munro to fix version check
    in ZPsycopgDA.
- Release 2.0.11:
  * lib/extras.py: fixed crash in fetchone() when prefetching using
    a RealDictCursor.
  * psycopg/cursor_ext.c: now raise correct exception when fetching
    using a custom row factory results in an error.
  * lib/extras.py: applied DictRow "diet" patch from Marko Kreen.
  * setup.py: applied patch from Elvis Pranskevichus to make
    PostgreSQL version detection more robust.</changelog>
  <changelog author="jnelson-suse@jamponi.net" date="1251201600">- Add --optimize=2 to build .pyo files, correct License and Url</changelog>
  <changelog author="termim@gmail.com" date="1288180800">- Update to 2.2.2:
    Bux fixes:
  * the call to logging.basicConfig() in pool.py has been dropped:
    it was messing with some projects using logging (and a library
    should not initialize the logging system anyway.)
  * psycopg now correctly handles time zones with seconds in the
    UTC offset. The old register_tstz_w_secs() function is deprecated
    and will raise a warning if called.
  * Exceptions raised by the column iterator are propagated.
  * Exceptions raised by executemany() interators are propagated.</changelog>
  <changelog author="elchevive@opensuse.org" date="1293451200">- Update to version 2.3.2</changelog>
  <changelog author="saschpe@suse.de" date="1298894400">- Spec file changes:
  * Added LICENSE and NEWS files
  * Added ZPL license to preamble (psycopg2 is dual-licensed)
  * Use upstream description
  * Fixed SLE build errors
  * Repacked tarball to bzip2
- Update to version 2.4
  * Added support for Python 3.1 and 3.2. The conversion has also
    brought several improvements:
  * Improvements to the named cusors and data handling
  * Fixed adaptation of None in composite types (ticket #26). Bug
    report by Karsten Hilbert.
  * Fixed several reference leaks in less common code paths.
  * Fixed segfault when a large object is closed and its connection no
    more available.
  * Added missing icon to ZPsycopgDA package, not available in Zope
    2.12.9 (ticket #30). Bug report and patch by Pumukel.
  * Fixed conversion of negative infinity (ticket #40). Bug report and
    patch by Marti Raudsepp.</changelog>
  <changelog author="saschpe@suse.de" date="1316606400">- Update to version 2.4.2:
  * connection.h: added codec attribute to avoid repeated codec name
    lookups during unicode query/params manipulations.
  * setup.py: bumped to version 2.3.2.dev0
  * psycopg/connection_int.c: applied patch from Marti Raudsepp to close
    ticket #24. Fixed segfault in connection when DateStyle not available
    (e.g.  pgbouncer appars not passing it to the client)
  * psycopg/utils.c: Added psycopg_strdup function.
  - See ChangeLog for more...
- Don't package testsuite
- Fix non-executable script rpmlint warning</changelog>
  <changelog author="jfunk@funktronics.ca" date="1326369600">- Update to 2.4.4:
  * register_composite() also works with the types implicitly defined after a
    table row, not only with the ones created by CREATE TYPE.
  * Values for the isolation level symbolic constants restored to what they
    were before release 2.4.2 to avoid breaking apps using the values instead
    of the constants.
  * Named DictCursor/RealDictCursor honour itersize (ticket #80).
  * Fixed rollback on error on Zope (ticket #73).
  * Raise DatabaseError instead of Error with empty libpq errors, consistently
    with other disconnection-related errors: regression introduced in release
    2.4.1 (ticket #82).
- Version 2.4.3:
  * connect() supports all the keyword arguments supported by the database
  * Added new_array_type() function for easy creation of array typecasters.
  * Added support for arrays of hstores and composite types (ticket #66).
  * Fixed segfault in case of transaction started with connection lost (and
    possibly other events).
  * Fixed adaptation of Decimal type in sub-interpreters, such as in certain
    mod_wsgi configurations (ticket #52).
  * Rollback connections in transaction or in error before putting them back
    into a pool. Also discard broken connections (ticket #62).
  * Lazy import of the slow uuid module, thanks to Marko Kreen.
  * Fixed NamedTupleCursor.executemany() (ticket #65).
  * Fixed --static-libpq setup option (ticket #64).
  * Fixed interaction between RealDictCursor and named cursors (ticket #67).
  * Dropped limit on the columns length in COPY operations (ticket #68).
  * Fixed reference leak with arguments referenced more than once in queries
    (ticket #81).
  * Fixed typecasting of arrays containing consecutive backslashes.
  * errorcodes map updated to PostgreSQL 9.1.</changelog>
  <changelog author="coolo@suse.com" date="1329134400">- patch license to follow spdx.org standard</changelog>
  <changelog author="saschpe@gmx.de" date="1331553600">- Simplify macro usage
- Remove outdated SUSE version checks</changelog>
  <changelog author="saschpe@suse.de" date="1332849600">- Can't hurt to suggest postgresql-server</changelog>
  <changelog author="jfunk@funktronics.ca" date="1333713600">- Update to 2.4.5:
  * The close() methods on connections and cursors don't raise exceptions
    if called on already closed objects.
  * Fixed fetchmany() with no argument in cursor subclasses
    (ticket #84).
  * Use lo_creat() instead of lo_create() when possible for better
    interaction with pgpool-II (ticket #88).
  * Error and its subclasses are picklable, useful for multiprocessing
    interaction (ticket #90).
  * Better efficiency and formatting of timezone offset objects thanks
    to Menno Smits (tickets #94, #95).
  * Fixed 'rownumber' during iteration on cursor subclasses.
    Regression introduced in 2.4.4 (ticket #100).
  * Added support for 'inet' arrays.
  * Fixed 'commit()' concurrency problem (ticket #103).
  * Codebase cleaned up using the GCC Python plugin's static analysis
    tool, which has revealed several unchecked return values, possible
    NULL dereferences, reference counting problems. Many thanks to David
    Malcolm for the useful tool and the assistance provided using it.</changelog>
  <changelog author="highwaystar.ru@gmail.com" date="1337947200">- python3 package added
- minor spec improvement</changelog>
  <changelog author="cfarrell@suse.com" date="1337947201">- license update: LGPL-3.0+ and (LGPL-3.0+ or ZPL-2.0) and
  SUSE-GPL-2.0-with-openssl-exception
  See the COPYING file. There are GPL-2.0+ (with openssl linking exceptions
  for pgsql) in the package. Also, the ZPL option is only available for one
  particular subdirectory in the package</changelog>
  <changelog author="jfunk@funktronics.ca" date="1366113600">- Update to 2.5:
  - Added JSON adaptation.
  - Added support for PostgreSQL 9.2 range types.
  - `connection` and `cursor` objects can be used in ``with`` statements as
    context managers as specified by recent DBAPI extension.
  - Added `psycopg2.extensions.Diagnostics` object to get extended info from
    a database error.  Many thanks to Matthew Woodcraft for the implementation
    (ticket #149).
  - Added `connection.cursor_factory` attribute to customize the default
    object returned by `connection.cursor()`.
  - Added support for backward scrollable cursors. Thanks to Jon Nelson for
    the initial patch (ticket #108).
  - Added a simple way to customize casting of composite types into Python
    objects other than namedtuples. Many thanks to Ronan Dunklau and Tobias
    Oberstein for the feature development.
  - `connection.reset()` implemented using `DISCARD ALL` on server versions
    supporting it.
  - Properly cleanup memory of broken connections (ticket #148).
  - Fixed bad interaction of ``setup.py`` with other dependencies in
    Distribute projects on Python 3 (ticket #153).
  - Added support for Python 3.3.
  - Dropped support for Python 2.4. Please use Psycopg 2.4.x if you need it.
  - `psycopg2.errorcodes` map updated to PostgreSQL 9.2.
  - Dropped Zope adapter from source repository. ZPsycopgDA now has its own
    project at &lt;http://github.com/psycopg/ZPsycopgDA&gt;.
- Changes from 2.4.6:
  - Fixed 'cursor()' arguments propagation in connection subclasses and
    overriding of the 'cursor_factory' argument. Thanks to Corry Haines for
    the report and the initial patch (ticket #105).
  - Dropped GIL release during string adaptation around a function call
    invoking a Python API function, which could cause interpreter crash.
    Thanks to Manu Cupcic for the report (ticket #110).
  - Close a green connection if there is an error in the callback. Maybe a
    harsh solution but it leaves the program responsive (ticket #113).
  - 'register_hstore()', 'register_composite()', 'tpc_recover()' work with
    RealDictConnection and Cursor (ticket #114).
  - Fixed broken pool for Zope and connections re-init across ZSQL methods in
    the same request (tickets #123, #125, #142).
  - connect() raises an exception instead of swallowing keyword arguments when
    a connection string is specified as well (ticket #131).
  - Discard any result produced by 'executemany()' (ticket #133).
  - Fixed pickling of FixedOffsetTimezone objects (ticket #135).
  - Release the GIL around PQgetResult calls after COPY (ticket #140).
  - Fixed empty strings handling in composite caster (ticket #141).
  - Fixed pickling of DictRow and RealDictRow objects.</changelog>
  <changelog author="dmueller@suse.com" date="1372161600">- update to 2.5.1:
  - Fixed build on Solaris 10 and 11 where the round() function is already
  declared (:ticket:`#146`).
  - Fixed comparison of `Range` with non-range objects (:ticket:`#164`).
  Thanks to Chris Withers for the patch.
  - Fixed double-free on connection dealloc (:ticket:`#166`). Thanks to
  Gangadharan S.A. for the report and fix suggestion.</changelog>
  <changelog author="dmueller@suse.com" date="1389614400">- update to 2.5.2:
  - Fixed segfault pickling the exception raised on connection error
  - Meaningful connection errors report a meaningful message
  - Manually creating `lobject` with the wrong parameter doesn't segfault</changelog>
  <changelog author="tbechtold@suse.com" date="1424779200">- update to version 2.6:
  - Added support for large objects larger than 2GB. Many thanks to Blake Rouse
    and the MAAS Team for the feature development.
  - Python `time` objects with a tzinfo specified and PostgreSQL :sql:`timetz`
    data are converted into each other (:ticket:`#272`).
  - Json apapter's `!str()` returns the adapted content instead of the `!repr()`
    (:ticket:`#191`).
  - Named cursors used as context manager don't swallow the exception on exit
    (:ticket:`#262`).
  - `cursor.description` can be pickled (:ticket:`#265`).
  - Propagate read error messages in COPY FROM (:ticket:`#270`).
  - PostgreSQL time 24:00 is converted to Python 00:00 (:ticket:`#278`).
  - Added :sql:`jsonb` support for PostgreSQL 9.4 (:ticket:`#226`).
  - Fixed segfault if COPY statements are passed to `~cursor.execute()` instead
    of using the proper methods (:ticket:`#219`).
  - Force conversion of pool arguments to integer to avoid potentially unbounded
    pools (:ticket:`#220`).
  - Cursors :sql:`WITH HOLD` don't begin a new transaction upon move/fetch/close
    (:ticket:`#228`).
  - Cursors :sql:`WITH HOLD` can be used in autocommit (:ticket:`#229`).
  - `~cursor.callproc()` doesn't silently ignore an argument without a length.
  - Fixed memory leak with large objects (:ticket:`#256`).
  - Make sure the internal ``_psycopg.so`` module can be imported stand-alone (to
    allow modules juggling such as the one described in :ticket:`#201`).
  - Work around `pip issue #1630 &lt;https://github.com/pypa/pip/issues/1630&gt;`__
    making installation via ``pip -e git+url`` impossible (:ticket:`#18`).
  - Copy operations correctly set the `cursor.rowcount` attribute
    (:ticket:`#180`).
  - It is now possible to call `get_transaction_status()` on closed connections.
  - Fixed unsafe access to object names causing assertion failures in
    Python 3 debug builds (:ticket:`#188`).
  - Mark the connection closed if found broken on `poll()` (from :ticket:`#192`
    discussion)
  - Fixed handling of dsn and closed attributes in connection subclasses
    failing to connect (from :ticket:`#192` discussion).
  - Added arbitrary but stable order to `Range` objects, thanks to
    Chris Withers (:ticket:`#193`).
  - Avoid blocking async connections on connect (:ticket:`#194`). Thanks to
    Adam Petrovich for the bug report and diagnosis.
  - Don't segfault using poorly defined cursor subclasses which forgot to call
    the superclass init (:ticket:`#195`).
  - Mark the connection closed when a Socket connection is broken, as it
    happens for TCP connections instead (:ticket:`#196`).
  - Fixed overflow opening a lobject with an oid not fitting in a signed int
    (:ticket:`#203`).
  - Fixed handling of explicit default ``cursor_factory=None`` in
    `connection.cursor()` (:ticket:`#210`).
  - Fixed possible segfault in named cursors creation.
  - Fixed debug build on Windows, thanks to James Emerton.
- Add python-Sphinx as BuilrRequires to build documenation. Also adjust
  the build process for html docs.</changelog>
  <changelog author="bwiedemann@suse.com" date="1457524800">- use the year from source gzip header instead of current one
  to make reproducible rpms</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- disable docs on SLE due to lack of python-Sphinx</changelog>
  <changelog author="dmueller@suse.com" date="1479124800">- update to 2.6.2:
  * Fixed inconsistent state in externally closed connections (tickets #263, #311, #443).
  * Report the server response status on errors (such as ticket #281).
  * Raise NotSupportedError on unhandled server response status (ticket #352).
  * Allow overriding string adapter encoding with no connection (ticket #331).
  * The wait_select callback allows interrupting a long-running query in an interactive shell using Ctrl-C (ticket #333).
  * Fixed PersistentConnectionPool on Python 3 (ticket #348).
  * Fixed segfault on repr() of an uninitialized connection (ticket #361).
  * Allow adapting bytes using QuotedString on Python 3 (ticket #365).
  * Added support for setuptools/wheel (ticket #370).
  * Fix build on Windows with Python 3.5, VS 2015 (ticket #380).
  * Fixed errorcodes.lookup initialization thread-safety (ticket #382).
  * Fixed read() exception propagation in copy_from (ticket #412).
  * Fixed possible NULL TZ decref (ticket #424).
  * errorcodes map updated to PostgreSQL 9.5.
  * Lists consisting of only None are escaped correctly (ticket #285).
  * Fixed deadlock in multithread programs using OpenSSL (ticket #290).
  * Correctly unlock the connection after error in flush (ticket #294).
  * Fixed MinTimeLoggingCursor.callproc() (ticket #309).
  * Added support for MSVC 2015 compiler (ticket #350).</changelog>
</package>
<package pkgid="511aaff384ec6018dcd06c93a8c7fe13ada47a51b2273d1963049b4c201282d3" name="python-psycopg2-debuginfo" arch="x86_64">
  <version epoch="0" ver="2.6.2" rel="3.17"/>
  <changelog author="jfunk@funktronics.ca" date="1250596800">- Update to 2.0.12:
  * psycopg/lobject_int.c: fixed problem with writing large data using
    lo_write: apparently the large objects code does not like non-blocking
    connections.
  * setup.py: fixed version detection for PostgreSQL rc, as
    suggested by Sok Ann Yap.
  * ZPsycopgDA/db.py: applied serialization error retry from Brian
    Sutherland.
  * Implemented connection.reset() method to reset the connection to
    well-know default parameters. This is much faster than closing and
    reopening the connection. (Suggested by a bug report by Glenn
    Maynard.)
  * psycopg/cursor_type.c: unified size macro definitions in COPY TO
    and COPY FROM operations: now the buffer for column names is 8192
    bytes that should be enough even for very large tables.
  * Applied patch from Robert Munro to fix version check
    in ZPsycopgDA.
- Release 2.0.11:
  * lib/extras.py: fixed crash in fetchone() when prefetching using
    a RealDictCursor.
  * psycopg/cursor_ext.c: now raise correct exception when fetching
    using a custom row factory results in an error.
  * lib/extras.py: applied DictRow "diet" patch from Marko Kreen.
  * setup.py: applied patch from Elvis Pranskevichus to make
    PostgreSQL version detection more robust.</changelog>
  <changelog author="jnelson-suse@jamponi.net" date="1251201600">- Add --optimize=2 to build .pyo files, correct License and Url</changelog>
  <changelog author="termim@gmail.com" date="1288180800">- Update to 2.2.2:
    Bux fixes:
  * the call to logging.basicConfig() in pool.py has been dropped:
    it was messing with some projects using logging (and a library
    should not initialize the logging system anyway.)
  * psycopg now correctly handles time zones with seconds in the
    UTC offset. The old register_tstz_w_secs() function is deprecated
    and will raise a warning if called.
  * Exceptions raised by the column iterator are propagated.
  * Exceptions raised by executemany() interators are propagated.</changelog>
  <changelog author="elchevive@opensuse.org" date="1293451200">- Update to version 2.3.2</changelog>
  <changelog author="saschpe@suse.de" date="1298894400">- Spec file changes:
  * Added LICENSE and NEWS files
  * Added ZPL license to preamble (psycopg2 is dual-licensed)
  * Use upstream description
  * Fixed SLE build errors
  * Repacked tarball to bzip2
- Update to version 2.4
  * Added support for Python 3.1 and 3.2. The conversion has also
    brought several improvements:
  * Improvements to the named cusors and data handling
  * Fixed adaptation of None in composite types (ticket #26). Bug
    report by Karsten Hilbert.
  * Fixed several reference leaks in less common code paths.
  * Fixed segfault when a large object is closed and its connection no
    more available.
  * Added missing icon to ZPsycopgDA package, not available in Zope
    2.12.9 (ticket #30). Bug report and patch by Pumukel.
  * Fixed conversion of negative infinity (ticket #40). Bug report and
    patch by Marti Raudsepp.</changelog>
  <changelog author="saschpe@suse.de" date="1316606400">- Update to version 2.4.2:
  * connection.h: added codec attribute to avoid repeated codec name
    lookups during unicode query/params manipulations.
  * setup.py: bumped to version 2.3.2.dev0
  * psycopg/connection_int.c: applied patch from Marti Raudsepp to close
    ticket #24. Fixed segfault in connection when DateStyle not available
    (e.g.  pgbouncer appars not passing it to the client)
  * psycopg/utils.c: Added psycopg_strdup function.
  - See ChangeLog for more...
- Don't package testsuite
- Fix non-executable script rpmlint warning</changelog>
  <changelog author="jfunk@funktronics.ca" date="1326369600">- Update to 2.4.4:
  * register_composite() also works with the types implicitly defined after a
    table row, not only with the ones created by CREATE TYPE.
  * Values for the isolation level symbolic constants restored to what they
    were before release 2.4.2 to avoid breaking apps using the values instead
    of the constants.
  * Named DictCursor/RealDictCursor honour itersize (ticket #80).
  * Fixed rollback on error on Zope (ticket #73).
  * Raise DatabaseError instead of Error with empty libpq errors, consistently
    with other disconnection-related errors: regression introduced in release
    2.4.1 (ticket #82).
- Version 2.4.3:
  * connect() supports all the keyword arguments supported by the database
  * Added new_array_type() function for easy creation of array typecasters.
  * Added support for arrays of hstores and composite types (ticket #66).
  * Fixed segfault in case of transaction started with connection lost (and
    possibly other events).
  * Fixed adaptation of Decimal type in sub-interpreters, such as in certain
    mod_wsgi configurations (ticket #52).
  * Rollback connections in transaction or in error before putting them back
    into a pool. Also discard broken connections (ticket #62).
  * Lazy import of the slow uuid module, thanks to Marko Kreen.
  * Fixed NamedTupleCursor.executemany() (ticket #65).
  * Fixed --static-libpq setup option (ticket #64).
  * Fixed interaction between RealDictCursor and named cursors (ticket #67).
  * Dropped limit on the columns length in COPY operations (ticket #68).
  * Fixed reference leak with arguments referenced more than once in queries
    (ticket #81).
  * Fixed typecasting of arrays containing consecutive backslashes.
  * errorcodes map updated to PostgreSQL 9.1.</changelog>
  <changelog author="coolo@suse.com" date="1329134400">- patch license to follow spdx.org standard</changelog>
  <changelog author="saschpe@gmx.de" date="1331553600">- Simplify macro usage
- Remove outdated SUSE version checks</changelog>
  <changelog author="saschpe@suse.de" date="1332849600">- Can't hurt to suggest postgresql-server</changelog>
  <changelog author="jfunk@funktronics.ca" date="1333713600">- Update to 2.4.5:
  * The close() methods on connections and cursors don't raise exceptions
    if called on already closed objects.
  * Fixed fetchmany() with no argument in cursor subclasses
    (ticket #84).
  * Use lo_creat() instead of lo_create() when possible for better
    interaction with pgpool-II (ticket #88).
  * Error and its subclasses are picklable, useful for multiprocessing
    interaction (ticket #90).
  * Better efficiency and formatting of timezone offset objects thanks
    to Menno Smits (tickets #94, #95).
  * Fixed 'rownumber' during iteration on cursor subclasses.
    Regression introduced in 2.4.4 (ticket #100).
  * Added support for 'inet' arrays.
  * Fixed 'commit()' concurrency problem (ticket #103).
  * Codebase cleaned up using the GCC Python plugin's static analysis
    tool, which has revealed several unchecked return values, possible
    NULL dereferences, reference counting problems. Many thanks to David
    Malcolm for the useful tool and the assistance provided using it.</changelog>
  <changelog author="highwaystar.ru@gmail.com" date="1337947200">- python3 package added
- minor spec improvement</changelog>
  <changelog author="cfarrell@suse.com" date="1337947201">- license update: LGPL-3.0+ and (LGPL-3.0+ or ZPL-2.0) and
  SUSE-GPL-2.0-with-openssl-exception
  See the COPYING file. There are GPL-2.0+ (with openssl linking exceptions
  for pgsql) in the package. Also, the ZPL option is only available for one
  particular subdirectory in the package</changelog>
  <changelog author="jfunk@funktronics.ca" date="1366113600">- Update to 2.5:
  - Added JSON adaptation.
  - Added support for PostgreSQL 9.2 range types.
  - `connection` and `cursor` objects can be used in ``with`` statements as
    context managers as specified by recent DBAPI extension.
  - Added `psycopg2.extensions.Diagnostics` object to get extended info from
    a database error.  Many thanks to Matthew Woodcraft for the implementation
    (ticket #149).
  - Added `connection.cursor_factory` attribute to customize the default
    object returned by `connection.cursor()`.
  - Added support for backward scrollable cursors. Thanks to Jon Nelson for
    the initial patch (ticket #108).
  - Added a simple way to customize casting of composite types into Python
    objects other than namedtuples. Many thanks to Ronan Dunklau and Tobias
    Oberstein for the feature development.
  - `connection.reset()` implemented using `DISCARD ALL` on server versions
    supporting it.
  - Properly cleanup memory of broken connections (ticket #148).
  - Fixed bad interaction of ``setup.py`` with other dependencies in
    Distribute projects on Python 3 (ticket #153).
  - Added support for Python 3.3.
  - Dropped support for Python 2.4. Please use Psycopg 2.4.x if you need it.
  - `psycopg2.errorcodes` map updated to PostgreSQL 9.2.
  - Dropped Zope adapter from source repository. ZPsycopgDA now has its own
    project at &lt;http://github.com/psycopg/ZPsycopgDA&gt;.
- Changes from 2.4.6:
  - Fixed 'cursor()' arguments propagation in connection subclasses and
    overriding of the 'cursor_factory' argument. Thanks to Corry Haines for
    the report and the initial patch (ticket #105).
  - Dropped GIL release during string adaptation around a function call
    invoking a Python API function, which could cause interpreter crash.
    Thanks to Manu Cupcic for the report (ticket #110).
  - Close a green connection if there is an error in the callback. Maybe a
    harsh solution but it leaves the program responsive (ticket #113).
  - 'register_hstore()', 'register_composite()', 'tpc_recover()' work with
    RealDictConnection and Cursor (ticket #114).
  - Fixed broken pool for Zope and connections re-init across ZSQL methods in
    the same request (tickets #123, #125, #142).
  - connect() raises an exception instead of swallowing keyword arguments when
    a connection string is specified as well (ticket #131).
  - Discard any result produced by 'executemany()' (ticket #133).
  - Fixed pickling of FixedOffsetTimezone objects (ticket #135).
  - Release the GIL around PQgetResult calls after COPY (ticket #140).
  - Fixed empty strings handling in composite caster (ticket #141).
  - Fixed pickling of DictRow and RealDictRow objects.</changelog>
  <changelog author="dmueller@suse.com" date="1372161600">- update to 2.5.1:
  - Fixed build on Solaris 10 and 11 where the round() function is already
  declared (:ticket:`#146`).
  - Fixed comparison of `Range` with non-range objects (:ticket:`#164`).
  Thanks to Chris Withers for the patch.
  - Fixed double-free on connection dealloc (:ticket:`#166`). Thanks to
  Gangadharan S.A. for the report and fix suggestion.</changelog>
  <changelog author="dmueller@suse.com" date="1389614400">- update to 2.5.2:
  - Fixed segfault pickling the exception raised on connection error
  - Meaningful connection errors report a meaningful message
  - Manually creating `lobject` with the wrong parameter doesn't segfault</changelog>
  <changelog author="tbechtold@suse.com" date="1424779200">- update to version 2.6:
  - Added support for large objects larger than 2GB. Many thanks to Blake Rouse
    and the MAAS Team for the feature development.
  - Python `time` objects with a tzinfo specified and PostgreSQL :sql:`timetz`
    data are converted into each other (:ticket:`#272`).
  - Json apapter's `!str()` returns the adapted content instead of the `!repr()`
    (:ticket:`#191`).
  - Named cursors used as context manager don't swallow the exception on exit
    (:ticket:`#262`).
  - `cursor.description` can be pickled (:ticket:`#265`).
  - Propagate read error messages in COPY FROM (:ticket:`#270`).
  - PostgreSQL time 24:00 is converted to Python 00:00 (:ticket:`#278`).
  - Added :sql:`jsonb` support for PostgreSQL 9.4 (:ticket:`#226`).
  - Fixed segfault if COPY statements are passed to `~cursor.execute()` instead
    of using the proper methods (:ticket:`#219`).
  - Force conversion of pool arguments to integer to avoid potentially unbounded
    pools (:ticket:`#220`).
  - Cursors :sql:`WITH HOLD` don't begin a new transaction upon move/fetch/close
    (:ticket:`#228`).
  - Cursors :sql:`WITH HOLD` can be used in autocommit (:ticket:`#229`).
  - `~cursor.callproc()` doesn't silently ignore an argument without a length.
  - Fixed memory leak with large objects (:ticket:`#256`).
  - Make sure the internal ``_psycopg.so`` module can be imported stand-alone (to
    allow modules juggling such as the one described in :ticket:`#201`).
  - Work around `pip issue #1630 &lt;https://github.com/pypa/pip/issues/1630&gt;`__
    making installation via ``pip -e git+url`` impossible (:ticket:`#18`).
  - Copy operations correctly set the `cursor.rowcount` attribute
    (:ticket:`#180`).
  - It is now possible to call `get_transaction_status()` on closed connections.
  - Fixed unsafe access to object names causing assertion failures in
    Python 3 debug builds (:ticket:`#188`).
  - Mark the connection closed if found broken on `poll()` (from :ticket:`#192`
    discussion)
  - Fixed handling of dsn and closed attributes in connection subclasses
    failing to connect (from :ticket:`#192` discussion).
  - Added arbitrary but stable order to `Range` objects, thanks to
    Chris Withers (:ticket:`#193`).
  - Avoid blocking async connections on connect (:ticket:`#194`). Thanks to
    Adam Petrovich for the bug report and diagnosis.
  - Don't segfault using poorly defined cursor subclasses which forgot to call
    the superclass init (:ticket:`#195`).
  - Mark the connection closed when a Socket connection is broken, as it
    happens for TCP connections instead (:ticket:`#196`).
  - Fixed overflow opening a lobject with an oid not fitting in a signed int
    (:ticket:`#203`).
  - Fixed handling of explicit default ``cursor_factory=None`` in
    `connection.cursor()` (:ticket:`#210`).
  - Fixed possible segfault in named cursors creation.
  - Fixed debug build on Windows, thanks to James Emerton.
- Add python-Sphinx as BuilrRequires to build documenation. Also adjust
  the build process for html docs.</changelog>
  <changelog author="bwiedemann@suse.com" date="1457524800">- use the year from source gzip header instead of current one
  to make reproducible rpms</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- disable docs on SLE due to lack of python-Sphinx</changelog>
  <changelog author="dmueller@suse.com" date="1479124800">- update to 2.6.2:
  * Fixed inconsistent state in externally closed connections (tickets #263, #311, #443).
  * Report the server response status on errors (such as ticket #281).
  * Raise NotSupportedError on unhandled server response status (ticket #352).
  * Allow overriding string adapter encoding with no connection (ticket #331).
  * The wait_select callback allows interrupting a long-running query in an interactive shell using Ctrl-C (ticket #333).
  * Fixed PersistentConnectionPool on Python 3 (ticket #348).
  * Fixed segfault on repr() of an uninitialized connection (ticket #361).
  * Allow adapting bytes using QuotedString on Python 3 (ticket #365).
  * Added support for setuptools/wheel (ticket #370).
  * Fix build on Windows with Python 3.5, VS 2015 (ticket #380).
  * Fixed errorcodes.lookup initialization thread-safety (ticket #382).
  * Fixed read() exception propagation in copy_from (ticket #412).
  * Fixed possible NULL TZ decref (ticket #424).
  * errorcodes map updated to PostgreSQL 9.5.
  * Lists consisting of only None are escaped correctly (ticket #285).
  * Fixed deadlock in multithread programs using OpenSSL (ticket #290).
  * Correctly unlock the connection after error in flush (ticket #294).
  * Fixed MinTimeLoggingCursor.callproc() (ticket #309).
  * Added support for MSVC 2015 compiler (ticket #350).</changelog>
</package>
<package pkgid="7dfbdfcad79d4bd11fb6e14d35933f9fca978926362fb9fdc4f7b59f2d6f93ff" name="python-psycopg2-debugsource" arch="x86_64">
  <version epoch="0" ver="2.6.2" rel="3.17"/>
  <changelog author="jfunk@funktronics.ca" date="1250596800">- Update to 2.0.12:
  * psycopg/lobject_int.c: fixed problem with writing large data using
    lo_write: apparently the large objects code does not like non-blocking
    connections.
  * setup.py: fixed version detection for PostgreSQL rc, as
    suggested by Sok Ann Yap.
  * ZPsycopgDA/db.py: applied serialization error retry from Brian
    Sutherland.
  * Implemented connection.reset() method to reset the connection to
    well-know default parameters. This is much faster than closing and
    reopening the connection. (Suggested by a bug report by Glenn
    Maynard.)
  * psycopg/cursor_type.c: unified size macro definitions in COPY TO
    and COPY FROM operations: now the buffer for column names is 8192
    bytes that should be enough even for very large tables.
  * Applied patch from Robert Munro to fix version check
    in ZPsycopgDA.
- Release 2.0.11:
  * lib/extras.py: fixed crash in fetchone() when prefetching using
    a RealDictCursor.
  * psycopg/cursor_ext.c: now raise correct exception when fetching
    using a custom row factory results in an error.
  * lib/extras.py: applied DictRow "diet" patch from Marko Kreen.
  * setup.py: applied patch from Elvis Pranskevichus to make
    PostgreSQL version detection more robust.</changelog>
  <changelog author="jnelson-suse@jamponi.net" date="1251201600">- Add --optimize=2 to build .pyo files, correct License and Url</changelog>
  <changelog author="termim@gmail.com" date="1288180800">- Update to 2.2.2:
    Bux fixes:
  * the call to logging.basicConfig() in pool.py has been dropped:
    it was messing with some projects using logging (and a library
    should not initialize the logging system anyway.)
  * psycopg now correctly handles time zones with seconds in the
    UTC offset. The old register_tstz_w_secs() function is deprecated
    and will raise a warning if called.
  * Exceptions raised by the column iterator are propagated.
  * Exceptions raised by executemany() interators are propagated.</changelog>
  <changelog author="elchevive@opensuse.org" date="1293451200">- Update to version 2.3.2</changelog>
  <changelog author="saschpe@suse.de" date="1298894400">- Spec file changes:
  * Added LICENSE and NEWS files
  * Added ZPL license to preamble (psycopg2 is dual-licensed)
  * Use upstream description
  * Fixed SLE build errors
  * Repacked tarball to bzip2
- Update to version 2.4
  * Added support for Python 3.1 and 3.2. The conversion has also
    brought several improvements:
  * Improvements to the named cusors and data handling
  * Fixed adaptation of None in composite types (ticket #26). Bug
    report by Karsten Hilbert.
  * Fixed several reference leaks in less common code paths.
  * Fixed segfault when a large object is closed and its connection no
    more available.
  * Added missing icon to ZPsycopgDA package, not available in Zope
    2.12.9 (ticket #30). Bug report and patch by Pumukel.
  * Fixed conversion of negative infinity (ticket #40). Bug report and
    patch by Marti Raudsepp.</changelog>
  <changelog author="saschpe@suse.de" date="1316606400">- Update to version 2.4.2:
  * connection.h: added codec attribute to avoid repeated codec name
    lookups during unicode query/params manipulations.
  * setup.py: bumped to version 2.3.2.dev0
  * psycopg/connection_int.c: applied patch from Marti Raudsepp to close
    ticket #24. Fixed segfault in connection when DateStyle not available
    (e.g.  pgbouncer appars not passing it to the client)
  * psycopg/utils.c: Added psycopg_strdup function.
  - See ChangeLog for more...
- Don't package testsuite
- Fix non-executable script rpmlint warning</changelog>
  <changelog author="jfunk@funktronics.ca" date="1326369600">- Update to 2.4.4:
  * register_composite() also works with the types implicitly defined after a
    table row, not only with the ones created by CREATE TYPE.
  * Values for the isolation level symbolic constants restored to what they
    were before release 2.4.2 to avoid breaking apps using the values instead
    of the constants.
  * Named DictCursor/RealDictCursor honour itersize (ticket #80).
  * Fixed rollback on error on Zope (ticket #73).
  * Raise DatabaseError instead of Error with empty libpq errors, consistently
    with other disconnection-related errors: regression introduced in release
    2.4.1 (ticket #82).
- Version 2.4.3:
  * connect() supports all the keyword arguments supported by the database
  * Added new_array_type() function for easy creation of array typecasters.
  * Added support for arrays of hstores and composite types (ticket #66).
  * Fixed segfault in case of transaction started with connection lost (and
    possibly other events).
  * Fixed adaptation of Decimal type in sub-interpreters, such as in certain
    mod_wsgi configurations (ticket #52).
  * Rollback connections in transaction or in error before putting them back
    into a pool. Also discard broken connections (ticket #62).
  * Lazy import of the slow uuid module, thanks to Marko Kreen.
  * Fixed NamedTupleCursor.executemany() (ticket #65).
  * Fixed --static-libpq setup option (ticket #64).
  * Fixed interaction between RealDictCursor and named cursors (ticket #67).
  * Dropped limit on the columns length in COPY operations (ticket #68).
  * Fixed reference leak with arguments referenced more than once in queries
    (ticket #81).
  * Fixed typecasting of arrays containing consecutive backslashes.
  * errorcodes map updated to PostgreSQL 9.1.</changelog>
  <changelog author="coolo@suse.com" date="1329134400">- patch license to follow spdx.org standard</changelog>
  <changelog author="saschpe@gmx.de" date="1331553600">- Simplify macro usage
- Remove outdated SUSE version checks</changelog>
  <changelog author="saschpe@suse.de" date="1332849600">- Can't hurt to suggest postgresql-server</changelog>
  <changelog author="jfunk@funktronics.ca" date="1333713600">- Update to 2.4.5:
  * The close() methods on connections and cursors don't raise exceptions
    if called on already closed objects.
  * Fixed fetchmany() with no argument in cursor subclasses
    (ticket #84).
  * Use lo_creat() instead of lo_create() when possible for better
    interaction with pgpool-II (ticket #88).
  * Error and its subclasses are picklable, useful for multiprocessing
    interaction (ticket #90).
  * Better efficiency and formatting of timezone offset objects thanks
    to Menno Smits (tickets #94, #95).
  * Fixed 'rownumber' during iteration on cursor subclasses.
    Regression introduced in 2.4.4 (ticket #100).
  * Added support for 'inet' arrays.
  * Fixed 'commit()' concurrency problem (ticket #103).
  * Codebase cleaned up using the GCC Python plugin's static analysis
    tool, which has revealed several unchecked return values, possible
    NULL dereferences, reference counting problems. Many thanks to David
    Malcolm for the useful tool and the assistance provided using it.</changelog>
  <changelog author="highwaystar.ru@gmail.com" date="1337947200">- python3 package added
- minor spec improvement</changelog>
  <changelog author="cfarrell@suse.com" date="1337947201">- license update: LGPL-3.0+ and (LGPL-3.0+ or ZPL-2.0) and
  SUSE-GPL-2.0-with-openssl-exception
  See the COPYING file. There are GPL-2.0+ (with openssl linking exceptions
  for pgsql) in the package. Also, the ZPL option is only available for one
  particular subdirectory in the package</changelog>
  <changelog author="jfunk@funktronics.ca" date="1366113600">- Update to 2.5:
  - Added JSON adaptation.
  - Added support for PostgreSQL 9.2 range types.
  - `connection` and `cursor` objects can be used in ``with`` statements as
    context managers as specified by recent DBAPI extension.
  - Added `psycopg2.extensions.Diagnostics` object to get extended info from
    a database error.  Many thanks to Matthew Woodcraft for the implementation
    (ticket #149).
  - Added `connection.cursor_factory` attribute to customize the default
    object returned by `connection.cursor()`.
  - Added support for backward scrollable cursors. Thanks to Jon Nelson for
    the initial patch (ticket #108).
  - Added a simple way to customize casting of composite types into Python
    objects other than namedtuples. Many thanks to Ronan Dunklau and Tobias
    Oberstein for the feature development.
  - `connection.reset()` implemented using `DISCARD ALL` on server versions
    supporting it.
  - Properly cleanup memory of broken connections (ticket #148).
  - Fixed bad interaction of ``setup.py`` with other dependencies in
    Distribute projects on Python 3 (ticket #153).
  - Added support for Python 3.3.
  - Dropped support for Python 2.4. Please use Psycopg 2.4.x if you need it.
  - `psycopg2.errorcodes` map updated to PostgreSQL 9.2.
  - Dropped Zope adapter from source repository. ZPsycopgDA now has its own
    project at &lt;http://github.com/psycopg/ZPsycopgDA&gt;.
- Changes from 2.4.6:
  - Fixed 'cursor()' arguments propagation in connection subclasses and
    overriding of the 'cursor_factory' argument. Thanks to Corry Haines for
    the report and the initial patch (ticket #105).
  - Dropped GIL release during string adaptation around a function call
    invoking a Python API function, which could cause interpreter crash.
    Thanks to Manu Cupcic for the report (ticket #110).
  - Close a green connection if there is an error in the callback. Maybe a
    harsh solution but it leaves the program responsive (ticket #113).
  - 'register_hstore()', 'register_composite()', 'tpc_recover()' work with
    RealDictConnection and Cursor (ticket #114).
  - Fixed broken pool for Zope and connections re-init across ZSQL methods in
    the same request (tickets #123, #125, #142).
  - connect() raises an exception instead of swallowing keyword arguments when
    a connection string is specified as well (ticket #131).
  - Discard any result produced by 'executemany()' (ticket #133).
  - Fixed pickling of FixedOffsetTimezone objects (ticket #135).
  - Release the GIL around PQgetResult calls after COPY (ticket #140).
  - Fixed empty strings handling in composite caster (ticket #141).
  - Fixed pickling of DictRow and RealDictRow objects.</changelog>
  <changelog author="dmueller@suse.com" date="1372161600">- update to 2.5.1:
  - Fixed build on Solaris 10 and 11 where the round() function is already
  declared (:ticket:`#146`).
  - Fixed comparison of `Range` with non-range objects (:ticket:`#164`).
  Thanks to Chris Withers for the patch.
  - Fixed double-free on connection dealloc (:ticket:`#166`). Thanks to
  Gangadharan S.A. for the report and fix suggestion.</changelog>
  <changelog author="dmueller@suse.com" date="1389614400">- update to 2.5.2:
  - Fixed segfault pickling the exception raised on connection error
  - Meaningful connection errors report a meaningful message
  - Manually creating `lobject` with the wrong parameter doesn't segfault</changelog>
  <changelog author="tbechtold@suse.com" date="1424779200">- update to version 2.6:
  - Added support for large objects larger than 2GB. Many thanks to Blake Rouse
    and the MAAS Team for the feature development.
  - Python `time` objects with a tzinfo specified and PostgreSQL :sql:`timetz`
    data are converted into each other (:ticket:`#272`).
  - Json apapter's `!str()` returns the adapted content instead of the `!repr()`
    (:ticket:`#191`).
  - Named cursors used as context manager don't swallow the exception on exit
    (:ticket:`#262`).
  - `cursor.description` can be pickled (:ticket:`#265`).
  - Propagate read error messages in COPY FROM (:ticket:`#270`).
  - PostgreSQL time 24:00 is converted to Python 00:00 (:ticket:`#278`).
  - Added :sql:`jsonb` support for PostgreSQL 9.4 (:ticket:`#226`).
  - Fixed segfault if COPY statements are passed to `~cursor.execute()` instead
    of using the proper methods (:ticket:`#219`).
  - Force conversion of pool arguments to integer to avoid potentially unbounded
    pools (:ticket:`#220`).
  - Cursors :sql:`WITH HOLD` don't begin a new transaction upon move/fetch/close
    (:ticket:`#228`).
  - Cursors :sql:`WITH HOLD` can be used in autocommit (:ticket:`#229`).
  - `~cursor.callproc()` doesn't silently ignore an argument without a length.
  - Fixed memory leak with large objects (:ticket:`#256`).
  - Make sure the internal ``_psycopg.so`` module can be imported stand-alone (to
    allow modules juggling such as the one described in :ticket:`#201`).
  - Work around `pip issue #1630 &lt;https://github.com/pypa/pip/issues/1630&gt;`__
    making installation via ``pip -e git+url`` impossible (:ticket:`#18`).
  - Copy operations correctly set the `cursor.rowcount` attribute
    (:ticket:`#180`).
  - It is now possible to call `get_transaction_status()` on closed connections.
  - Fixed unsafe access to object names causing assertion failures in
    Python 3 debug builds (:ticket:`#188`).
  - Mark the connection closed if found broken on `poll()` (from :ticket:`#192`
    discussion)
  - Fixed handling of dsn and closed attributes in connection subclasses
    failing to connect (from :ticket:`#192` discussion).
  - Added arbitrary but stable order to `Range` objects, thanks to
    Chris Withers (:ticket:`#193`).
  - Avoid blocking async connections on connect (:ticket:`#194`). Thanks to
    Adam Petrovich for the bug report and diagnosis.
  - Don't segfault using poorly defined cursor subclasses which forgot to call
    the superclass init (:ticket:`#195`).
  - Mark the connection closed when a Socket connection is broken, as it
    happens for TCP connections instead (:ticket:`#196`).
  - Fixed overflow opening a lobject with an oid not fitting in a signed int
    (:ticket:`#203`).
  - Fixed handling of explicit default ``cursor_factory=None`` in
    `connection.cursor()` (:ticket:`#210`).
  - Fixed possible segfault in named cursors creation.
  - Fixed debug build on Windows, thanks to James Emerton.
- Add python-Sphinx as BuilrRequires to build documenation. Also adjust
  the build process for html docs.</changelog>
  <changelog author="bwiedemann@suse.com" date="1457524800">- use the year from source gzip header instead of current one
  to make reproducible rpms</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- disable docs on SLE due to lack of python-Sphinx</changelog>
  <changelog author="dmueller@suse.com" date="1479124800">- update to 2.6.2:
  * Fixed inconsistent state in externally closed connections (tickets #263, #311, #443).
  * Report the server response status on errors (such as ticket #281).
  * Raise NotSupportedError on unhandled server response status (ticket #352).
  * Allow overriding string adapter encoding with no connection (ticket #331).
  * The wait_select callback allows interrupting a long-running query in an interactive shell using Ctrl-C (ticket #333).
  * Fixed PersistentConnectionPool on Python 3 (ticket #348).
  * Fixed segfault on repr() of an uninitialized connection (ticket #361).
  * Allow adapting bytes using QuotedString on Python 3 (ticket #365).
  * Added support for setuptools/wheel (ticket #370).
  * Fix build on Windows with Python 3.5, VS 2015 (ticket #380).
  * Fixed errorcodes.lookup initialization thread-safety (ticket #382).
  * Fixed read() exception propagation in copy_from (ticket #412).
  * Fixed possible NULL TZ decref (ticket #424).
  * errorcodes map updated to PostgreSQL 9.5.
  * Lists consisting of only None are escaped correctly (ticket #285).
  * Fixed deadlock in multithread programs using OpenSSL (ticket #290).
  * Correctly unlock the connection after error in flush (ticket #294).
  * Fixed MinTimeLoggingCursor.callproc() (ticket #309).
  * Added support for MSVC 2015 compiler (ticket #350).</changelog>
</package>
<package pkgid="3d18616e4d0dc2e40ff44bfbc4d7610076e91480b771fa8bdb4008daa21b3032" name="python-psycopg2-doc" arch="x86_64">
  <version epoch="0" ver="2.6.2" rel="3.17"/>
  <changelog author="jfunk@funktronics.ca" date="1250596800">- Update to 2.0.12:
  * psycopg/lobject_int.c: fixed problem with writing large data using
    lo_write: apparently the large objects code does not like non-blocking
    connections.
  * setup.py: fixed version detection for PostgreSQL rc, as
    suggested by Sok Ann Yap.
  * ZPsycopgDA/db.py: applied serialization error retry from Brian
    Sutherland.
  * Implemented connection.reset() method to reset the connection to
    well-know default parameters. This is much faster than closing and
    reopening the connection. (Suggested by a bug report by Glenn
    Maynard.)
  * psycopg/cursor_type.c: unified size macro definitions in COPY TO
    and COPY FROM operations: now the buffer for column names is 8192
    bytes that should be enough even for very large tables.
  * Applied patch from Robert Munro to fix version check
    in ZPsycopgDA.
- Release 2.0.11:
  * lib/extras.py: fixed crash in fetchone() when prefetching using
    a RealDictCursor.
  * psycopg/cursor_ext.c: now raise correct exception when fetching
    using a custom row factory results in an error.
  * lib/extras.py: applied DictRow "diet" patch from Marko Kreen.
  * setup.py: applied patch from Elvis Pranskevichus to make
    PostgreSQL version detection more robust.</changelog>
  <changelog author="jnelson-suse@jamponi.net" date="1251201600">- Add --optimize=2 to build .pyo files, correct License and Url</changelog>
  <changelog author="termim@gmail.com" date="1288180800">- Update to 2.2.2:
    Bux fixes:
  * the call to logging.basicConfig() in pool.py has been dropped:
    it was messing with some projects using logging (and a library
    should not initialize the logging system anyway.)
  * psycopg now correctly handles time zones with seconds in the
    UTC offset. The old register_tstz_w_secs() function is deprecated
    and will raise a warning if called.
  * Exceptions raised by the column iterator are propagated.
  * Exceptions raised by executemany() interators are propagated.</changelog>
  <changelog author="elchevive@opensuse.org" date="1293451200">- Update to version 2.3.2</changelog>
  <changelog author="saschpe@suse.de" date="1298894400">- Spec file changes:
  * Added LICENSE and NEWS files
  * Added ZPL license to preamble (psycopg2 is dual-licensed)
  * Use upstream description
  * Fixed SLE build errors
  * Repacked tarball to bzip2
- Update to version 2.4
  * Added support for Python 3.1 and 3.2. The conversion has also
    brought several improvements:
  * Improvements to the named cusors and data handling
  * Fixed adaptation of None in composite types (ticket #26). Bug
    report by Karsten Hilbert.
  * Fixed several reference leaks in less common code paths.
  * Fixed segfault when a large object is closed and its connection no
    more available.
  * Added missing icon to ZPsycopgDA package, not available in Zope
    2.12.9 (ticket #30). Bug report and patch by Pumukel.
  * Fixed conversion of negative infinity (ticket #40). Bug report and
    patch by Marti Raudsepp.</changelog>
  <changelog author="saschpe@suse.de" date="1316606400">- Update to version 2.4.2:
  * connection.h: added codec attribute to avoid repeated codec name
    lookups during unicode query/params manipulations.
  * setup.py: bumped to version 2.3.2.dev0
  * psycopg/connection_int.c: applied patch from Marti Raudsepp to close
    ticket #24. Fixed segfault in connection when DateStyle not available
    (e.g.  pgbouncer appars not passing it to the client)
  * psycopg/utils.c: Added psycopg_strdup function.
  - See ChangeLog for more...
- Don't package testsuite
- Fix non-executable script rpmlint warning</changelog>
  <changelog author="jfunk@funktronics.ca" date="1326369600">- Update to 2.4.4:
  * register_composite() also works with the types implicitly defined after a
    table row, not only with the ones created by CREATE TYPE.
  * Values for the isolation level symbolic constants restored to what they
    were before release 2.4.2 to avoid breaking apps using the values instead
    of the constants.
  * Named DictCursor/RealDictCursor honour itersize (ticket #80).
  * Fixed rollback on error on Zope (ticket #73).
  * Raise DatabaseError instead of Error with empty libpq errors, consistently
    with other disconnection-related errors: regression introduced in release
    2.4.1 (ticket #82).
- Version 2.4.3:
  * connect() supports all the keyword arguments supported by the database
  * Added new_array_type() function for easy creation of array typecasters.
  * Added support for arrays of hstores and composite types (ticket #66).
  * Fixed segfault in case of transaction started with connection lost (and
    possibly other events).
  * Fixed adaptation of Decimal type in sub-interpreters, such as in certain
    mod_wsgi configurations (ticket #52).
  * Rollback connections in transaction or in error before putting them back
    into a pool. Also discard broken connections (ticket #62).
  * Lazy import of the slow uuid module, thanks to Marko Kreen.
  * Fixed NamedTupleCursor.executemany() (ticket #65).
  * Fixed --static-libpq setup option (ticket #64).
  * Fixed interaction between RealDictCursor and named cursors (ticket #67).
  * Dropped limit on the columns length in COPY operations (ticket #68).
  * Fixed reference leak with arguments referenced more than once in queries
    (ticket #81).
  * Fixed typecasting of arrays containing consecutive backslashes.
  * errorcodes map updated to PostgreSQL 9.1.</changelog>
  <changelog author="coolo@suse.com" date="1329134400">- patch license to follow spdx.org standard</changelog>
  <changelog author="saschpe@gmx.de" date="1331553600">- Simplify macro usage
- Remove outdated SUSE version checks</changelog>
  <changelog author="saschpe@suse.de" date="1332849600">- Can't hurt to suggest postgresql-server</changelog>
  <changelog author="jfunk@funktronics.ca" date="1333713600">- Update to 2.4.5:
  * The close() methods on connections and cursors don't raise exceptions
    if called on already closed objects.
  * Fixed fetchmany() with no argument in cursor subclasses
    (ticket #84).
  * Use lo_creat() instead of lo_create() when possible for better
    interaction with pgpool-II (ticket #88).
  * Error and its subclasses are picklable, useful for multiprocessing
    interaction (ticket #90).
  * Better efficiency and formatting of timezone offset objects thanks
    to Menno Smits (tickets #94, #95).
  * Fixed 'rownumber' during iteration on cursor subclasses.
    Regression introduced in 2.4.4 (ticket #100).
  * Added support for 'inet' arrays.
  * Fixed 'commit()' concurrency problem (ticket #103).
  * Codebase cleaned up using the GCC Python plugin's static analysis
    tool, which has revealed several unchecked return values, possible
    NULL dereferences, reference counting problems. Many thanks to David
    Malcolm for the useful tool and the assistance provided using it.</changelog>
  <changelog author="highwaystar.ru@gmail.com" date="1337947200">- python3 package added
- minor spec improvement</changelog>
  <changelog author="cfarrell@suse.com" date="1337947201">- license update: LGPL-3.0+ and (LGPL-3.0+ or ZPL-2.0) and
  SUSE-GPL-2.0-with-openssl-exception
  See the COPYING file. There are GPL-2.0+ (with openssl linking exceptions
  for pgsql) in the package. Also, the ZPL option is only available for one
  particular subdirectory in the package</changelog>
  <changelog author="jfunk@funktronics.ca" date="1366113600">- Update to 2.5:
  - Added JSON adaptation.
  - Added support for PostgreSQL 9.2 range types.
  - `connection` and `cursor` objects can be used in ``with`` statements as
    context managers as specified by recent DBAPI extension.
  - Added `psycopg2.extensions.Diagnostics` object to get extended info from
    a database error.  Many thanks to Matthew Woodcraft for the implementation
    (ticket #149).
  - Added `connection.cursor_factory` attribute to customize the default
    object returned by `connection.cursor()`.
  - Added support for backward scrollable cursors. Thanks to Jon Nelson for
    the initial patch (ticket #108).
  - Added a simple way to customize casting of composite types into Python
    objects other than namedtuples. Many thanks to Ronan Dunklau and Tobias
    Oberstein for the feature development.
  - `connection.reset()` implemented using `DISCARD ALL` on server versions
    supporting it.
  - Properly cleanup memory of broken connections (ticket #148).
  - Fixed bad interaction of ``setup.py`` with other dependencies in
    Distribute projects on Python 3 (ticket #153).
  - Added support for Python 3.3.
  - Dropped support for Python 2.4. Please use Psycopg 2.4.x if you need it.
  - `psycopg2.errorcodes` map updated to PostgreSQL 9.2.
  - Dropped Zope adapter from source repository. ZPsycopgDA now has its own
    project at &lt;http://github.com/psycopg/ZPsycopgDA&gt;.
- Changes from 2.4.6:
  - Fixed 'cursor()' arguments propagation in connection subclasses and
    overriding of the 'cursor_factory' argument. Thanks to Corry Haines for
    the report and the initial patch (ticket #105).
  - Dropped GIL release during string adaptation around a function call
    invoking a Python API function, which could cause interpreter crash.
    Thanks to Manu Cupcic for the report (ticket #110).
  - Close a green connection if there is an error in the callback. Maybe a
    harsh solution but it leaves the program responsive (ticket #113).
  - 'register_hstore()', 'register_composite()', 'tpc_recover()' work with
    RealDictConnection and Cursor (ticket #114).
  - Fixed broken pool for Zope and connections re-init across ZSQL methods in
    the same request (tickets #123, #125, #142).
  - connect() raises an exception instead of swallowing keyword arguments when
    a connection string is specified as well (ticket #131).
  - Discard any result produced by 'executemany()' (ticket #133).
  - Fixed pickling of FixedOffsetTimezone objects (ticket #135).
  - Release the GIL around PQgetResult calls after COPY (ticket #140).
  - Fixed empty strings handling in composite caster (ticket #141).
  - Fixed pickling of DictRow and RealDictRow objects.</changelog>
  <changelog author="dmueller@suse.com" date="1372161600">- update to 2.5.1:
  - Fixed build on Solaris 10 and 11 where the round() function is already
  declared (:ticket:`#146`).
  - Fixed comparison of `Range` with non-range objects (:ticket:`#164`).
  Thanks to Chris Withers for the patch.
  - Fixed double-free on connection dealloc (:ticket:`#166`). Thanks to
  Gangadharan S.A. for the report and fix suggestion.</changelog>
  <changelog author="dmueller@suse.com" date="1389614400">- update to 2.5.2:
  - Fixed segfault pickling the exception raised on connection error
  - Meaningful connection errors report a meaningful message
  - Manually creating `lobject` with the wrong parameter doesn't segfault</changelog>
  <changelog author="tbechtold@suse.com" date="1424779200">- update to version 2.6:
  - Added support for large objects larger than 2GB. Many thanks to Blake Rouse
    and the MAAS Team for the feature development.
  - Python `time` objects with a tzinfo specified and PostgreSQL :sql:`timetz`
    data are converted into each other (:ticket:`#272`).
  - Json apapter's `!str()` returns the adapted content instead of the `!repr()`
    (:ticket:`#191`).
  - Named cursors used as context manager don't swallow the exception on exit
    (:ticket:`#262`).
  - `cursor.description` can be pickled (:ticket:`#265`).
  - Propagate read error messages in COPY FROM (:ticket:`#270`).
  - PostgreSQL time 24:00 is converted to Python 00:00 (:ticket:`#278`).
  - Added :sql:`jsonb` support for PostgreSQL 9.4 (:ticket:`#226`).
  - Fixed segfault if COPY statements are passed to `~cursor.execute()` instead
    of using the proper methods (:ticket:`#219`).
  - Force conversion of pool arguments to integer to avoid potentially unbounded
    pools (:ticket:`#220`).
  - Cursors :sql:`WITH HOLD` don't begin a new transaction upon move/fetch/close
    (:ticket:`#228`).
  - Cursors :sql:`WITH HOLD` can be used in autocommit (:ticket:`#229`).
  - `~cursor.callproc()` doesn't silently ignore an argument without a length.
  - Fixed memory leak with large objects (:ticket:`#256`).
  - Make sure the internal ``_psycopg.so`` module can be imported stand-alone (to
    allow modules juggling such as the one described in :ticket:`#201`).
  - Work around `pip issue #1630 &lt;https://github.com/pypa/pip/issues/1630&gt;`__
    making installation via ``pip -e git+url`` impossible (:ticket:`#18`).
  - Copy operations correctly set the `cursor.rowcount` attribute
    (:ticket:`#180`).
  - It is now possible to call `get_transaction_status()` on closed connections.
  - Fixed unsafe access to object names causing assertion failures in
    Python 3 debug builds (:ticket:`#188`).
  - Mark the connection closed if found broken on `poll()` (from :ticket:`#192`
    discussion)
  - Fixed handling of dsn and closed attributes in connection subclasses
    failing to connect (from :ticket:`#192` discussion).
  - Added arbitrary but stable order to `Range` objects, thanks to
    Chris Withers (:ticket:`#193`).
  - Avoid blocking async connections on connect (:ticket:`#194`). Thanks to
    Adam Petrovich for the bug report and diagnosis.
  - Don't segfault using poorly defined cursor subclasses which forgot to call
    the superclass init (:ticket:`#195`).
  - Mark the connection closed when a Socket connection is broken, as it
    happens for TCP connections instead (:ticket:`#196`).
  - Fixed overflow opening a lobject with an oid not fitting in a signed int
    (:ticket:`#203`).
  - Fixed handling of explicit default ``cursor_factory=None`` in
    `connection.cursor()` (:ticket:`#210`).
  - Fixed possible segfault in named cursors creation.
  - Fixed debug build on Windows, thanks to James Emerton.
- Add python-Sphinx as BuilrRequires to build documenation. Also adjust
  the build process for html docs.</changelog>
  <changelog author="bwiedemann@suse.com" date="1457524800">- use the year from source gzip header instead of current one
  to make reproducible rpms</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- disable docs on SLE due to lack of python-Sphinx</changelog>
  <changelog author="dmueller@suse.com" date="1479124800">- update to 2.6.2:
  * Fixed inconsistent state in externally closed connections (tickets #263, #311, #443).
  * Report the server response status on errors (such as ticket #281).
  * Raise NotSupportedError on unhandled server response status (ticket #352).
  * Allow overriding string adapter encoding with no connection (ticket #331).
  * The wait_select callback allows interrupting a long-running query in an interactive shell using Ctrl-C (ticket #333).
  * Fixed PersistentConnectionPool on Python 3 (ticket #348).
  * Fixed segfault on repr() of an uninitialized connection (ticket #361).
  * Allow adapting bytes using QuotedString on Python 3 (ticket #365).
  * Added support for setuptools/wheel (ticket #370).
  * Fix build on Windows with Python 3.5, VS 2015 (ticket #380).
  * Fixed errorcodes.lookup initialization thread-safety (ticket #382).
  * Fixed read() exception propagation in copy_from (ticket #412).
  * Fixed possible NULL TZ decref (ticket #424).
  * errorcodes map updated to PostgreSQL 9.5.
  * Lists consisting of only None are escaped correctly (ticket #285).
  * Fixed deadlock in multithread programs using OpenSSL (ticket #290).
  * Correctly unlock the connection after error in flush (ticket #294).
  * Fixed MinTimeLoggingCursor.callproc() (ticket #309).
  * Added support for MSVC 2015 compiler (ticket #350).</changelog>
</package>
<package pkgid="61db93969ae91b3885aba334fa444ce6cb1bc5090e3be0e25277f198bb61146c" name="repmgr" arch="noarch">
  <version epoch="0" ver="3.3" rel="1.1"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="dab70fe8bf0f022b9fefa597d98fdf470fc6d78cf43655f86df26cda83e324a6" name="repmgr" arch="src">
  <version epoch="0" ver="3.3" rel="1.1"/>
  <changelog author="darin@darins.net" date="1362139200">- Initial packaging of repmgr
- Setup packaging to support multiple postgres versions
- Used update-alternatives</changelog>
  <changelog author="darin@darins.net" date="1362398400">- Adding missing build requirements
- Added realname define and set naming to pgname-rename
- own contrib dir</changelog>
  <changelog author="darin@darins.net" date="1410264000">- Update to 2.0
  See release notes for a full listing of changes
    http://www.repmgr.org/release-notes-2.0.html
- fix license</changelog>
  <changelog author="mrueckert@suse.de" date="1424347200">- update to 2.0.2
  - see http://www.repmgr.org/release-notes-2.0.2.html
- enable 9.4 build</changelog>
  <changelog author="mrueckert@suse.de" date="1461585600">- update to 3.1.2
  This drops support for postgresql &lt; 9.3
- changes from 3.1.2
  - Fix pg_ctl path generation in do_standby_switchover() (Ian)
  - Regularly sync witness server repl_nodes table (Ian)
  - Documentation improvements (Gianni, dhyannataraj)
  - (Experimental) ensure repmgr handles failover slots when
    copying in rsync mode (Craig, Ian)
  - rsync mode handling fixes (Martín)
  - Enable repmgr to compile against 9.6devel (Ian)
- changes from 3.1.1
  - Add '-P/--pwprompt' option for "repmgr create witness" (Ian)
  - Prevent repmgr/repmgrd running as root (Ian)
- changes from 3.1.0
  - Add "repmgr standby switchover" command (Ian)
  - Revised README file (Ian)
  - Remove requirement for 'archive_mode' to be enabled (Ian)
  - Improve -?/--help output, showing default values if relevant
    (Ian)
  - Various bugfixes to command line/configuration parameter
    handling (Ian)
- changes from 3.0.3
  - Create replication slot if required before base backup is run
    (Abhijit)
  - standy clone: when using rsync, clean up "pg_replslot"
    directory (Ian)
  - Improve --help output (Ian)
  - Improve config file parsing (Ian)
  - Various logging output improvements, including explicit HINTS
    (Ian)
  - Add --log-level to explicitly set log level on command line
    (Ian)
  - Repurpose --verbose to display extra log output (Ian)
  - Add --terse to hide hints and other non-critical output (Ian)
  - Reference internal functions with explicit catalog path (Ian)
  - When following a new primary, have repmgr (not repmgrd) create
    the new slot (Ian)
  - Add /etc/repmgr.conf as a default configuration file location
    (Ian)
  - Prevent repmgrd's -v/--verbose option expecting a parameter
    (Ian)
  - Prevent invalid replication_lag values being written to the
    monitoring table (Ian)
  - Improve repmgrd behaviour when monitored standby node is
    temporarily unavailable (Martín)
- changes from 3.0.2
  - Improve handling of --help/--version options; and improve help
    output (Ian)
  - Improve handling of situation where logfile can't be opened
    (Ian)
  - Always pass -D/--pgdata option to pg_basebackup (Ian)
  - Bugfix: standby clone --force does not empty pg_xlog (Gianni)
  - Bugfix: autofailover with reconnect_attempts &gt; 1 (Gianni)
  - Bugfix: ignore comments after values (soxwellfb)
  - Bugfix: handle string values in 'node' parameter correctly
    (Gregory Duchatelet)
  - Allow repmgr to be compiled with a newer libpq (Marco)
  - Bugfix: call update_node_record_set_upstream() for STANDBY
    FOLLOW (Tomas)
  - Update `repmgr --help` output (per Github report from renard)
  - Update tablespace remapping in --rsync-only mode for 9.5 and
    later (Ian)
  - Deprecate `-l/--local-port` option - the port can be extracted
    from the conninfo string in repmgr.conf (Ian)
  - Add STANDBY UNREGISTER (Vik Fearing)
  - Don't fail with error when registering master if schema already
    defined (Ian)
  - Fixes to whitespace handling when parsing config file (Ian)
- changes from 3.0.1
  - Prevent repmgrd from looping infinitely if node was not
    registered (Ian)
  - When promoting a standby, have repmgr (not repmgrd) handle
    metadata updates (Ian)
  - Re-use replication slot if it already exists (Ian)
  - Prevent a test SSH connection being made when not needed (Ian)
  - Correct monitoring table column names (Ian)
- changes from 3.0
  - Require PostgreSQL 9.3 or later (Ian)
  - Use `pg_basebackup` by default (instead of `rsync`) to clone
    standby servers (Ian)
  - Use `pg_ctl promote` to promote a standby to primary
  - Enable tablespace remapping using `pg_basebackup` (in
    PostgreSQL 9.3 with `rsync`) (Ian)
  - Support cascaded standbys (Ian)
  - "pg_bindir" no longer required as a configuration parameter
    (Ian)
  - Enable replication slots to be used (PostgreSQL 9.4 and later
    (Ian)
  - Command line option "--check-upstream-config" (Ian)
  - Add event logging table and option to execute an external
    program when an event occurs (Ian)
  - General usability and logging message improvements (Ian)
  - Code consolidation and cleanup (Ian)
- changes from 2.0.3
  - Add -S/--superuser option for witness database creation Ian)
  - Add -c/--fast-checkpoint option for cloning (Christoph)
  - Add option "--initdb-no-pwprompt" (Ian)</changelog>
  <changelog author="mrueckert@suse.de" date="1470744000">- update to 3.1.4
  http://www.repmgr.org/release-notes-3.1.4.html
  http://www.repmgr.org/release-notes-3.1.3.html</changelog>
  <changelog author="mrueckert@suse.de" date="1470744001">- fix the horribly broken update-alternatives scriptlet</changelog>
  <changelog author="mrueckert@suse.de" date="1471348800">- update to 3.1.5
  - The repmgr cluster show command will no longer display database
    connection error messages unless the --verbose option is used.
  - repmgrd's handling of failover events when failover=manual has
    been improved and a new event notification
    standby_disconnect_manual will notify if a standby with this
    setting has been disconnected from replication.
  - Additional event notifications standby_switchover and
    standby_follow
  - Improved replication and apply lag calculation with repmgrd
    monitoring enables (-m/--monitoring-history)
  - Improved repmgr standby switchover operations.</changelog>
  <changelog author="mrueckert@suse.de" date="1476446400">- let plugins provide repmgr-implementation and require that from
  the main package
- provide init integration for repmgrd</changelog>
  <changelog author="mrueckert@suse.de" date="1486728000">- update to 3.3
  - repmgr: always log to STDERR even if log facility defined (Ian)
  - repmgr: add --log-to-file to log repmgr output to the defined
    log facility (Ian)
  - repmgr: improve handling of command line parameter errors (Ian)
  - repmgr: add option --upstream-conninfo to explicitly set
    'primary_conninfo' in recovery.conf (Ian)
  - repmgr: enable a standby to be registered which isn't running
    (Ian)
  - repmgr: enable `standby register --force` to update a node
    record with cascaded downstream node records (Ian)
  - repmgr: add option `--no-conninfo-password` (Abhijit, Ian)
  - repmgr: add initial support for PostgreSQL 10.0 (Ian)
  - repmgr: escape values in primary_conninfo if needed (Ian)
  - repmgr: require a valid repmgr cluster name unless -F/--force
    supplied (Ian)
  - repmgr: check master server is registered with repmgr before
    cloning (Ian)
  - repmgr: ensure data directory defaults to that of the source
    node (Ian)
  - repmgr: various fixes to Barman cloning mode (Gianni, Ian)
  - repmgr: fix `repmgr cluster crosscheck` output (Ian)
  - repmgr: add support for cloning from a Barman backup (Gianni)
  - repmgr: add commands `standby matrix` and `standby crosscheck`
    (Gianni)
  - repmgr: suppress connection error display in `repmgr cluster
    show` unless `--verbose` supplied (Ian)
  - repmgr: add commands `witness register` and `witness
    unregister` (Ian)
  - repmgr: enable `standby unregister` / `witness unregister` to
    be executed for a node which is not running (Ian)
  - repmgr: remove deprecated command line options
  - -initdb-no-pwprompt and -l/--local-port (Ian)
  - repmgr: before cloning with pg_basebackup, check that
    sufficient free walsenders are available (Ian)
  - repmgr: add option `--wait-sync` for `standby register` which
    causes repmgr to wait for the registered node record to
    synchronise to the standby (Ian)
  - repmgr: add option `--copy-external-config-files` for files
    outside of the data directory (Ian)
  - repmgr: only require `wal_keep_segments` to be set in certain
    corner cases (Ian)
  - repmgr: better support cloning from a node other than the one
    to stream from (Ian)
  - repmgrd: add configuration options to override the default
    pg_ctl commands (Jarkko Oranen, Ian)
  - repmgrd: don't start if node is inactive and failover=automatic
    (Ian)</changelog>
</package>
<package pkgid="dbe6e9413d5e247698241f53dad0ec9718e205c746ed33b2ee544c1407d4c464" name="skytools" arch="src">
  <version epoch="0" ver="3.2" rel="2.3"/>
  <changelog author="mrueckert@suse.de" date="1396267200">- initial package</changelog>
  <changelog author="mrueckert@suse.de" date="1396267201">- use pg 9.1 on sles 11</changelog>
  <changelog author="mrueckert@suse.de" date="1396267202">- add requires for runtime deps</changelog>
  <changelog author="mrueckert@suse.de" date="1396440000">- fix license tag, it is ISC.</changelog>
  <changelog author="zawel1@gmail.com" date="1409745600">- version 3.2</changelog>
  <changelog author="mpluskal@suse.com" date="1467115200">- Fix building
- Spec file cleanup by spec-cleaner</changelog>
</package>
<package pkgid="19e4eab6d030deacbeb1652bb2f8a0167a5eb497ba0a79b9c3280175d2e3346e" name="skytools" arch="x86_64">
  <version epoch="0" ver="3.2" rel="2.3"/>
  <changelog author="mrueckert@suse.de" date="1396267200">- initial package</changelog>
  <changelog author="mrueckert@suse.de" date="1396267201">- use pg 9.1 on sles 11</changelog>
  <changelog author="mrueckert@suse.de" date="1396267202">- add requires for runtime deps</changelog>
  <changelog author="mrueckert@suse.de" date="1396440000">- fix license tag, it is ISC.</changelog>
  <changelog author="zawel1@gmail.com" date="1409745600">- version 3.2</changelog>
  <changelog author="mpluskal@suse.com" date="1467115200">- Fix building
- Spec file cleanup by spec-cleaner</changelog>
</package>
<package pkgid="2b94f15d000594618294ed8fabc80ca10b80bff07a42bcf0cc4d0d51971c0cc8" name="skytools-debuginfo" arch="x86_64">
  <version epoch="0" ver="3.2" rel="2.3"/>
  <changelog author="mrueckert@suse.de" date="1396267200">- initial package</changelog>
  <changelog author="mrueckert@suse.de" date="1396267201">- use pg 9.1 on sles 11</changelog>
  <changelog author="mrueckert@suse.de" date="1396267202">- add requires for runtime deps</changelog>
  <changelog author="mrueckert@suse.de" date="1396440000">- fix license tag, it is ISC.</changelog>
  <changelog author="zawel1@gmail.com" date="1409745600">- version 3.2</changelog>
  <changelog author="mpluskal@suse.com" date="1467115200">- Fix building
- Spec file cleanup by spec-cleaner</changelog>
</package>
<package pkgid="9fc82bc9cce68029d2585ab41228ea2a5e7a940da07a58e99d39b883351c5a44" name="skytools-debugsource" arch="x86_64">
  <version epoch="0" ver="3.2" rel="2.3"/>
  <changelog author="mrueckert@suse.de" date="1396267200">- initial package</changelog>
  <changelog author="mrueckert@suse.de" date="1396267201">- use pg 9.1 on sles 11</changelog>
  <changelog author="mrueckert@suse.de" date="1396267202">- add requires for runtime deps</changelog>
  <changelog author="mrueckert@suse.de" date="1396440000">- fix license tag, it is ISC.</changelog>
  <changelog author="zawel1@gmail.com" date="1409745600">- version 3.2</changelog>
  <changelog author="mpluskal@suse.com" date="1467115200">- Fix building
- Spec file cleanup by spec-cleaner</changelog>
</package>
</otherdata>