Index index by Group index by Distribution index by Vendor index by creation date index by Name Mirrors Help Search

postgresql96-contrib-9.6.17-lp152.1.1 RPM for aarch64

From OpenSuSE Ports Leap 15.2 for aarch64

Name: postgresql96-contrib Distribution: openSUSE Leap 15.2
Version: 9.6.17 Vendor: openSUSE
Release: lp152.1.1 Build date: Fri Mar 13 11:17:36 2020
Group: Productivity/Databases/Tools Build host: obs-arm-7
Size: 5247303 Source RPM: postgresql96-9.6.17-lp152.1.1.src.rpm
Packager: https://bugs.opensuse.org
Url: https://www.postgresql.org/
Summary: Contributed Extensions and Additions to PostgreSQL
PostgreSQL is an advanced object-relational database management system
that supports an extended subset of the SQL standard, including
transactions, foreign keys, subqueries, triggers, and user-defined
types and functions.

The postgresql-contrib package includes extensions and additions that
are distributed along with the PostgreSQL sources, but are not (yet)
officially part of the PostgreSQL core.

Documentation for the modules contained in this package can be found in
/usr/share/doc/packages/postgresql/contrib.

Provides

Requires

License

PostgreSQL

Changelog

* Sat Feb 15 2020 Marcus Rueckert <mrueckert@suse.de>
  - update to 9.6.17 (CVE-2020-1720)
    https://www.postgresql.org/about/news/2011/
    https://www.postgresql.org/docs/9.6/release-9-6-17.html
* Sun Dec 29 2019 Lars Vogdt <lars@linux-schulserver.de>
  - use and package the sha256 checksum for for source
* Fri Dec 20 2019 Marcus Rueckert <mrueckert@suse.de>
  - update to 9.6.16:
    https://www.postgresql.org/about/news/1994/
    https://www.postgresql.org/docs/9.6/release-9-6-16.html
* Tue Oct 22 2019 Marcus Rueckert <mrueckert@suse.de>
  - add requires to the devel package for the libs that are returned
    by pg_config --libs
* Mon Aug 12 2019 Reinhard Max <max@suse.com>
  - Update to 9.6.15:
    * https://www.postgresql.org/about/news/1960/
    * https://www.postgresql.org/docs/9.6/release-9-6-15.html
    * CVE-2019-10208, bsc#1145092: TYPE in pg_temp executes arbitrary
      SQL during SECURITY DEFINER execution.
* Fri Aug 02 2019 Martin Liška <mliska@suse.cz>
  - Use FAT LTO objects in order to provide proper static library.
* Fri Jun 21 2019 Marcus Rueckert <mrueckert@suse.de>
  - Update to 9.6.14:
    https://www.postgresql.org/docs/9.6/release-9-6-14.html
* Fri May 10 2019 Reinhard Max <max@suse.com>
  - Update to 9.6.13:
    * https://www.postgresql.org/docs/9.6/release-9-6-13.html
    * https://www.postgresql.org/about/news/1939/
    * CVE-2019-10130, bsc#1134689: Prevent row-level security
      policies from being bypassed via selectivity estimators.
* Tue Mar 05 2019 Reinhard Max <max@suse.com>
  - Make the server-devel package exclusive across versions.
* Mon Feb 25 2019 Reinhard Max <max@suse.com>
  - Update to 9.6.12:
    * https://www.postgresql.org/docs/9.6/release-9-6-12.html
    * https://www.postgresql.org/about/news/1920/
    * By default, panic instead of retrying after fsync() failure,
      to avoid possible data corruption.
    * Numerous other bug fixes.
  - Overhaul README.SUSE
* Fri Nov 09 2018 Reinhard Max <max@suse.com>
  - Update to 9.6.11:
    * Numerous bug fixes, see the release notes:
      https://www.postgresql.org/docs/9.6/release-9-6-11.html
    * Remove unneeded library dependencies from PGXS.
* Wed Oct 17 2018 Marcus Rueckert <mrueckert@suse.de>
  - add provides for the new server-devel package that will be
    introduced in postgresql 11
* Fri Aug 10 2018 max@suse.com
  - Update to 9.6.10:
    https://www.postgresql.org/docs/current/static/release-9-6-10.html
    * CVE-2018-10915, bsc#1104199: Fix failure to reset libpq's state
      fully between connection attempts.
    * CVE-2018-10925, bsc#1104202: Fix INSERT ... ON CONFLICT UPDATE
      through a view that isn't just SELECT * FROM ...
* Wed May 16 2018 max@suse.com
  - Update to 9.6.9:
    https://www.postgresql.org/about/news/1851/
    https://www.postgresql.org/docs/current/static/release-9-6-9.html
    A dump/restore is not required for those running 9.6.X.
    However, if you use the adminpack extension, you should update
    it as per the first changelog entry below.
    Also, if the function marking mistakes mentioned in the second
    and third changelog entries below affect you, you will want to
    take steps to correct your database catalogs.
    * CVE-2018-1115, bsc#1091610: Remove public execute privilege
      from contrib/adminpack's pg_logfile_rotate() function
      pg_logfile_rotate() is a deprecated wrapper for the core
      function pg_rotate_logfile(). When that function was changed
      to rely on SQL privileges for access control rather than a
      hard-coded superuser check, pg_logfile_rotate() should have
      been updated as well, but the need for this was missed. Hence,
      if adminpack is installed, any user could request a logfile
      rotation, creating a minor security issue.
      After installing this update, administrators should update
      adminpack by performing ALTER EXTENSION adminpack UPDATE in
      each database in which adminpack is installed.
    * Fix incorrect volatility markings on a few built-in functions
    * Fix incorrect parallel-safety markings on a few built-in
      functions.
* Sat Mar 10 2018 mrueckert@suse.de
  - Update to PostgreSQL 9.6.8
    * https://www.postgresql.org/docs/9.6/static/release-9-6-8.html
      A dump/restore is not required for those running 9.6.X.
      However, if you run an installation in which not all users are
      mutually trusting, or if you maintain an application or
      extension that is intended for use in arbitrary situations, it
      is strongly recommended that you read the documentation changes
      described in the first changelog entry in the link above, and
      take suitable steps to ensure that your installation or code is
      secure.
      Also, the changes described in the second changelog entry in
      the link above may cause functions used in index expressions or
      materialized views to fail during auto-analyze, or when
      reloading from a dump. After upgrading, monitor the server logs
      for such problems, and fix affected functions.
    * CVE-2018-1058 bsc#1081925 Uncontrolled search path element in
      pg_dump and other client applications
* Fri Feb 09 2018 max@suse.com
  - Update to PostgreSQL 9.6.7
    * https://www.postgresql.org/docs/9.6/static/release-9-6-7.html
    * CVE-2018-1053, bsc#1077983: Ensure that all temporary files
      made by pg_upgrade are non-world-readable.
    * bsc#1079757: Rename pg_rewind's copy_file_range function to
      avoid conflict with new Linux system call of that name.
  - Don't %config the symlinks to /etc/alternatives to avoid rpmlint
    warnings.
* Tue Dec 05 2017 mrueckert@suse.de
  - Update to version 9.6.6:
    * https://www.postgresql.org/docs/9.6/static/release-9-6-6.html
    * Security Issues
    - CVE-2017-15098, bsc#1067844:
      Memory disclosure in JSON functions
    - CVE-2017-15099, bsc#1067841: INSERT ... ON CONFLICT DO UPDATE
      fails to enforce SELECT privileges
      Prior to this release, the "INSERT ... ON CONFLICT DO UPDATE"
      would not check to see if the executing user had permission
      to perform a "SELECT" on the index performing the conflicting
      check. Additionally, in a table with row-level security
      enabled, the "INSERT ... ON CONFLICT DO UPDATE" would not
      check the SELECT policies for that table before performing
      the update.
      This fix ensures that "INSERT ... ON CONFLICT DO UPDATE"
      checks against table permissions and RLS policies before
      executing.
* Thu Nov 23 2017 mrueckert@suse.de
  - port /usr/share/postgresql/install-alternatives usage to the new
    scheme
* Fri Nov 03 2017 max@suse.com
  - Simplify the set of local RPM macros.
  - Use /usr/share/postgresql/install-alternatives in the respective
    scriptlets.
  - Fix the logic around restart on upgrade and stop on removal.
    We bring the binaries, but we don't own the unit file.
* Mon Oct 02 2017 max@suse.com
  - Break a build dependency loop in the server packages that led to
    bootstrap problems.
* Fri Sep 22 2017 max@suse.com
  - Adjust dependencies to the new packaging schema.
  - Build the libs in 10 rather than 9.6.
* Fri Sep 01 2017 max@suse.com
  - Update to version 9.6.5:
    * https://www.postgresql.org/docs/9.6/static/release-9-6-5.html
    * Show foreign tables in information_schema.table_privileges
      view.
    * Clean up handling of a fatal exit (e.g., due to receipt of
      SIGTERM) that occurs while trying to execute a ROLLBACK of a
      failed transaction.
    * Remove assertion that could trigger during a fatal exit.
    * Correctly identify columns that are of a range type or domain
      type over a composite type or domain type being searched for.
    * Prevent crash when passing fixed-length pass-by-reference data
      types to parallel worker processe.
    * Fix crash in pg_restore when using parallel mode and using a
      list file to select a subset of items to restore.
    * Change ecpg's parser to allow RETURNING clauses without
      attached C variables.
    * Change ecpg's parser to recognize backslash continuation of C
      preprocessor command lines.
* Fri Aug 11 2017 max@suse.com
  - Update to version 9.6.4:
    * https://www.postgresql.org/docs/9.6/static/release-9-6-4.html
    * CVE-2017-7547, bsc#1051685: Further restrict visibility of
      pg_user_mappings.umoptions, to protect passwords stored as
      user mapping options.
    * CVE-2017-7546, bsc#1051684: Disallow empty passwords in all
      password-based authentication methods.
    * CVE-2017-7548, bsc#1053259: lo_put() function ignores ACLs.
* Thu Aug 10 2017 mrueckert@suse.de
  - fix building on sle11 by using krb5-devel again
* Fri Aug 04 2017 mrueckert@suse.de
  - use multibuild
* Wed May 17 2017 dimstar@opensuse.org
  - Replace krb5-devel BuildRequires with pkgconfig(krb5): allow OBS
    to deliver krb5-mini when applicable.
* Thu May 11 2017 max@suse.com
  - 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).
* Wed Mar 15 2017 astieger@suse.com
  - fix tests with timezone 2017a
    postgresql-9.6.2-fix-timezone-tests.patch
* Thu Feb 09 2017 mrueckert@suse.de
  - 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
* Sun Oct 30 2016 13ilya@gmail.com
  - 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
* Mon Oct 10 2016 max@suse.com
  - Build the libs in 9.6 rather then 9.5.
* Sun Oct 02 2016 mrueckert@suse.de
  - 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
* Fri Aug 12 2016 fweiss@suse.com
  - 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.
* Tue Aug 09 2016 mrueckert@suse.de
  - 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.
* Fri Jun 24 2016 mrueckert@suse.de
  - 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.
* Thu May 12 2016 mrueckert@suse.de
  - 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
* Wed May 04 2016 mrueckert@suse.de
  - 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
* Wed May 04 2016 mrueckert@suse.de
  - 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
* Fri Feb 12 2016 max@suse.com
  - 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
* Tue Feb 09 2016 max@suse.com
  - 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
* Mon Oct 12 2015 max@suse.com
  - 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.
* Thu Oct 08 2015 max@suse.com
  - Make sure that plpgsql.h gets installed, because pldebugger
    needs it.
* Mon Sep 28 2015 max@suse.com
  - Move ~postgres/.bash_profile to postgresql-server to avoid a
    file conflict between the versioned server packages.
* Tue Jul 21 2015 max@suse.com
  - Bring PostgreSQL 9.4 to SLE12 (fate#319049).
* Fri Jun 26 2015 max@suse.com
  - 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
* Thu Feb 19 2015 max@suse.com
  - 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
* Wed Feb 18 2015 max@suse.com
  - 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
* Thu Feb 12 2015 mrueckert@suse.de
  - majorversion should only be 9.4
* Fri Feb 06 2015 darin@darins.net
  - 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.
* Fri Jan 16 2015 darin@darins.net
  - removed %pgbasedir from contrib and server package
* Tue Dec 23 2014 darin@darins.net
  - Update to 9.4.0
    Major enhancements in PostgreSQL 9.4 include:
    * Add jsonb, a more capable and efficient data type for storing JSON data
    * Add new SQL command ALTER SYSTEM for changing postgresql.conf configuration file entries
    * Reduce lock strength for some ALTER TABLE commands
    * Allow materialized views to be refreshed without blocking concurrent reads
    * Add support for logical decoding of WAL data, to allow database changes to be streamed out in a customizable format
    * Allow background worker processes to be dynamically registered, started and terminated
    * See release notes for a full list of changes:
      http://www.postgresql.org/docs/9.4/static/release-9-4.html

Files

/etc/alternatives/oid2name
/etc/alternatives/pg_archivecleanup
/etc/alternatives/pg_standby
/etc/alternatives/pg_test_fsync
/etc/alternatives/pg_test_timing
/etc/alternatives/pg_upgrade
/etc/alternatives/pg_xlogdump
/etc/alternatives/pgbench
/etc/alternatives/vacuumlo
/usr/bin/oid2name
/usr/bin/pg_archivecleanup
/usr/bin/pg_standby
/usr/bin/pg_test_fsync
/usr/bin/pg_test_timing
/usr/bin/pg_upgrade
/usr/bin/pg_xlogdump
/usr/bin/pgbench
/usr/bin/vacuumlo
/usr/lib/postgresql
/usr/lib/postgresql96/bin/oid2name
/usr/lib/postgresql96/bin/pg_archivecleanup
/usr/lib/postgresql96/bin/pg_standby
/usr/lib/postgresql96/bin/pg_test_fsync
/usr/lib/postgresql96/bin/pg_test_timing
/usr/lib/postgresql96/bin/pg_upgrade
/usr/lib/postgresql96/bin/pg_xlogdump
/usr/lib/postgresql96/bin/pgbench
/usr/lib/postgresql96/bin/vacuumlo
/usr/lib/postgresql96/lib64/_int.so
/usr/lib/postgresql96/lib64/adminpack.so
/usr/lib/postgresql96/lib64/auth_delay.so
/usr/lib/postgresql96/lib64/auto_explain.so
/usr/lib/postgresql96/lib64/autoinc.so
/usr/lib/postgresql96/lib64/bloom.so
/usr/lib/postgresql96/lib64/btree_gin.so
/usr/lib/postgresql96/lib64/btree_gist.so
/usr/lib/postgresql96/lib64/chkpass.so
/usr/lib/postgresql96/lib64/citext.so
/usr/lib/postgresql96/lib64/cube.so
/usr/lib/postgresql96/lib64/dblink.so
/usr/lib/postgresql96/lib64/dict_int.so
/usr/lib/postgresql96/lib64/dict_xsyn.so
/usr/lib/postgresql96/lib64/earthdistance.so
/usr/lib/postgresql96/lib64/file_fdw.so
/usr/lib/postgresql96/lib64/fuzzystrmatch.so
/usr/lib/postgresql96/lib64/hstore.so
/usr/lib/postgresql96/lib64/hstore_plperl.so
/usr/lib/postgresql96/lib64/hstore_plpython2.so
/usr/lib/postgresql96/lib64/insert_username.so
/usr/lib/postgresql96/lib64/isn.so
/usr/lib/postgresql96/lib64/lo.so
/usr/lib/postgresql96/lib64/ltree.so
/usr/lib/postgresql96/lib64/ltree_plpython2.so
/usr/lib/postgresql96/lib64/moddatetime.so
/usr/lib/postgresql96/lib64/pageinspect.so
/usr/lib/postgresql96/lib64/passwordcheck.so
/usr/lib/postgresql96/lib64/pg_buffercache.so
/usr/lib/postgresql96/lib64/pg_freespacemap.so
/usr/lib/postgresql96/lib64/pg_prewarm.so
/usr/lib/postgresql96/lib64/pg_stat_statements.so
/usr/lib/postgresql96/lib64/pg_trgm.so
/usr/lib/postgresql96/lib64/pg_visibility.so
/usr/lib/postgresql96/lib64/pgcrypto.so
/usr/lib/postgresql96/lib64/pgrowlocks.so
/usr/lib/postgresql96/lib64/pgstattuple.so
/usr/lib/postgresql96/lib64/pgxml.so
/usr/lib/postgresql96/lib64/postgres_fdw.so
/usr/lib/postgresql96/lib64/refint.so
/usr/lib/postgresql96/lib64/seg.so
/usr/lib/postgresql96/lib64/sslinfo.so
/usr/lib/postgresql96/lib64/tablefunc.so
/usr/lib/postgresql96/lib64/tcn.so
/usr/lib/postgresql96/lib64/test_decoding.so
/usr/lib/postgresql96/lib64/timetravel.so
/usr/lib/postgresql96/lib64/tsearch2.so
/usr/lib/postgresql96/lib64/tsm_system_rows.so
/usr/lib/postgresql96/lib64/tsm_system_time.so
/usr/lib/postgresql96/lib64/unaccent.so
/usr/lib/postgresql96/lib64/uuid-ossp.so
/usr/share/doc/packages/postgresql96
/usr/share/doc/packages/postgresql96/extension
/usr/share/doc/packages/postgresql96/extension/autoinc.example
/usr/share/doc/packages/postgresql96/extension/insert_username.example
/usr/share/doc/packages/postgresql96/extension/moddatetime.example
/usr/share/doc/packages/postgresql96/extension/refint.example
/usr/share/doc/packages/postgresql96/extension/timetravel.example
/usr/share/man/man1/oid2name.1pg96.gz
/usr/share/man/man1/pg_archivecleanup.1pg96.gz
/usr/share/man/man1/pg_standby.1pg96.gz
/usr/share/man/man1/pg_test_fsync.1pg96.gz
/usr/share/man/man1/pg_test_timing.1pg96.gz
/usr/share/man/man1/pg_upgrade.1pg96.gz
/usr/share/man/man1/pg_xlogdump.1pg96.gz
/usr/share/man/man1/pgbench.1pg96.gz
/usr/share/man/man1/vacuumlo.1pg96.gz
/usr/share/postgresql96
/usr/share/postgresql96/extension/adminpack--1.0--1.1.sql
/usr/share/postgresql96/extension/adminpack--1.0.sql
/usr/share/postgresql96/extension/adminpack--1.1.sql
/usr/share/postgresql96/extension/adminpack.control
/usr/share/postgresql96/extension/autoinc--1.0.sql
/usr/share/postgresql96/extension/autoinc--unpackaged--1.0.sql
/usr/share/postgresql96/extension/autoinc.control
/usr/share/postgresql96/extension/bloom--1.0.sql
/usr/share/postgresql96/extension/bloom.control
/usr/share/postgresql96/extension/btree_gin--1.0.sql
/usr/share/postgresql96/extension/btree_gin--unpackaged--1.0.sql
/usr/share/postgresql96/extension/btree_gin.control
/usr/share/postgresql96/extension/btree_gist--1.0--1.1.sql
/usr/share/postgresql96/extension/btree_gist--1.1--1.2.sql
/usr/share/postgresql96/extension/btree_gist--1.2.sql
/usr/share/postgresql96/extension/btree_gist--unpackaged--1.0.sql
/usr/share/postgresql96/extension/btree_gist.control
/usr/share/postgresql96/extension/chkpass--1.0.sql
/usr/share/postgresql96/extension/chkpass--unpackaged--1.0.sql
/usr/share/postgresql96/extension/chkpass.control
/usr/share/postgresql96/extension/citext--1.0--1.1.sql
/usr/share/postgresql96/extension/citext--1.1--1.2.sql
/usr/share/postgresql96/extension/citext--1.2--1.3.sql
/usr/share/postgresql96/extension/citext--1.3.sql
/usr/share/postgresql96/extension/citext--unpackaged--1.0.sql
/usr/share/postgresql96/extension/citext.control
/usr/share/postgresql96/extension/cube--1.0--1.1.sql
/usr/share/postgresql96/extension/cube--1.1--1.2.sql
/usr/share/postgresql96/extension/cube--1.2.sql
/usr/share/postgresql96/extension/cube--unpackaged--1.0.sql
/usr/share/postgresql96/extension/cube.control
/usr/share/postgresql96/extension/dblink--1.0--1.1.sql
/usr/share/postgresql96/extension/dblink--1.1--1.2.sql
/usr/share/postgresql96/extension/dblink--1.2.sql
/usr/share/postgresql96/extension/dblink--unpackaged--1.0.sql
/usr/share/postgresql96/extension/dblink.control
/usr/share/postgresql96/extension/dict_int--1.0.sql
/usr/share/postgresql96/extension/dict_int--unpackaged--1.0.sql
/usr/share/postgresql96/extension/dict_int.control
/usr/share/postgresql96/extension/dict_xsyn--1.0.sql
/usr/share/postgresql96/extension/dict_xsyn--unpackaged--1.0.sql
/usr/share/postgresql96/extension/dict_xsyn.control
/usr/share/postgresql96/extension/earthdistance--1.0--1.1.sql
/usr/share/postgresql96/extension/earthdistance--1.1.sql
/usr/share/postgresql96/extension/earthdistance--unpackaged--1.0.sql
/usr/share/postgresql96/extension/earthdistance.control
/usr/share/postgresql96/extension/file_fdw--1.0.sql
/usr/share/postgresql96/extension/file_fdw.control
/usr/share/postgresql96/extension/fuzzystrmatch--1.0--1.1.sql
/usr/share/postgresql96/extension/fuzzystrmatch--1.1.sql
/usr/share/postgresql96/extension/fuzzystrmatch--unpackaged--1.0.sql
/usr/share/postgresql96/extension/fuzzystrmatch.control
/usr/share/postgresql96/extension/hstore--1.0--1.1.sql
/usr/share/postgresql96/extension/hstore--1.1--1.2.sql
/usr/share/postgresql96/extension/hstore--1.2--1.3.sql
/usr/share/postgresql96/extension/hstore--1.3--1.4.sql
/usr/share/postgresql96/extension/hstore--1.4.sql
/usr/share/postgresql96/extension/hstore--unpackaged--1.0.sql
/usr/share/postgresql96/extension/hstore.control
/usr/share/postgresql96/extension/hstore_plperl--1.0.sql
/usr/share/postgresql96/extension/hstore_plperl.control
/usr/share/postgresql96/extension/hstore_plperlu--1.0.sql
/usr/share/postgresql96/extension/hstore_plperlu.control
/usr/share/postgresql96/extension/hstore_plpython2u--1.0.sql
/usr/share/postgresql96/extension/hstore_plpython2u.control
/usr/share/postgresql96/extension/hstore_plpython3u--1.0.sql
/usr/share/postgresql96/extension/hstore_plpython3u.control
/usr/share/postgresql96/extension/hstore_plpythonu--1.0.sql
/usr/share/postgresql96/extension/hstore_plpythonu.control
/usr/share/postgresql96/extension/insert_username--1.0.sql
/usr/share/postgresql96/extension/insert_username--unpackaged--1.0.sql
/usr/share/postgresql96/extension/insert_username.control
/usr/share/postgresql96/extension/intagg--1.0--1.1.sql
/usr/share/postgresql96/extension/intagg--1.1.sql
/usr/share/postgresql96/extension/intagg--unpackaged--1.0.sql
/usr/share/postgresql96/extension/intagg.control
/usr/share/postgresql96/extension/intarray--1.0--1.1.sql
/usr/share/postgresql96/extension/intarray--1.1--1.2.sql
/usr/share/postgresql96/extension/intarray--1.2.sql
/usr/share/postgresql96/extension/intarray--unpackaged--1.0.sql
/usr/share/postgresql96/extension/intarray.control
/usr/share/postgresql96/extension/isn--1.0--1.1.sql
/usr/share/postgresql96/extension/isn--1.1.sql
/usr/share/postgresql96/extension/isn--unpackaged--1.0.sql
/usr/share/postgresql96/extension/isn.control
/usr/share/postgresql96/extension/lo--1.0--1.1.sql
/usr/share/postgresql96/extension/lo--1.1.sql
/usr/share/postgresql96/extension/lo--unpackaged--1.0.sql
/usr/share/postgresql96/extension/lo.control
/usr/share/postgresql96/extension/ltree--1.0--1.1.sql
/usr/share/postgresql96/extension/ltree--1.1.sql
/usr/share/postgresql96/extension/ltree--unpackaged--1.0.sql
/usr/share/postgresql96/extension/ltree.control
/usr/share/postgresql96/extension/ltree_plpython2u--1.0.sql
/usr/share/postgresql96/extension/ltree_plpython2u.control
/usr/share/postgresql96/extension/ltree_plpython3u--1.0.sql
/usr/share/postgresql96/extension/ltree_plpython3u.control
/usr/share/postgresql96/extension/ltree_plpythonu--1.0.sql
/usr/share/postgresql96/extension/ltree_plpythonu.control
/usr/share/postgresql96/extension/moddatetime--1.0.sql
/usr/share/postgresql96/extension/moddatetime--unpackaged--1.0.sql
/usr/share/postgresql96/extension/moddatetime.control
/usr/share/postgresql96/extension/pageinspect--1.0--1.1.sql
/usr/share/postgresql96/extension/pageinspect--1.1--1.2.sql
/usr/share/postgresql96/extension/pageinspect--1.2--1.3.sql
/usr/share/postgresql96/extension/pageinspect--1.3--1.4.sql
/usr/share/postgresql96/extension/pageinspect--1.4--1.5.sql
/usr/share/postgresql96/extension/pageinspect--1.5.sql
/usr/share/postgresql96/extension/pageinspect--unpackaged--1.0.sql
/usr/share/postgresql96/extension/pageinspect.control
/usr/share/postgresql96/extension/pg_buffercache--1.0--1.1.sql
/usr/share/postgresql96/extension/pg_buffercache--1.1--1.2.sql
/usr/share/postgresql96/extension/pg_buffercache--1.2.sql
/usr/share/postgresql96/extension/pg_buffercache--unpackaged--1.0.sql
/usr/share/postgresql96/extension/pg_buffercache.control
/usr/share/postgresql96/extension/pg_freespacemap--1.0--1.1.sql
/usr/share/postgresql96/extension/pg_freespacemap--1.1.sql
/usr/share/postgresql96/extension/pg_freespacemap--unpackaged--1.0.sql
/usr/share/postgresql96/extension/pg_freespacemap.control
/usr/share/postgresql96/extension/pg_prewarm--1.0--1.1.sql
/usr/share/postgresql96/extension/pg_prewarm--1.1.sql
/usr/share/postgresql96/extension/pg_prewarm.control
/usr/share/postgresql96/extension/pg_stat_statements--1.0--1.1.sql
/usr/share/postgresql96/extension/pg_stat_statements--1.1--1.2.sql
/usr/share/postgresql96/extension/pg_stat_statements--1.2--1.3.sql
/usr/share/postgresql96/extension/pg_stat_statements--1.3--1.4.sql
/usr/share/postgresql96/extension/pg_stat_statements--1.4.sql
/usr/share/postgresql96/extension/pg_stat_statements--unpackaged--1.0.sql
/usr/share/postgresql96/extension/pg_stat_statements.control
/usr/share/postgresql96/extension/pg_trgm--1.0--1.1.sql
/usr/share/postgresql96/extension/pg_trgm--1.1--1.2.sql
/usr/share/postgresql96/extension/pg_trgm--1.2--1.3.sql
/usr/share/postgresql96/extension/pg_trgm--1.3.sql
/usr/share/postgresql96/extension/pg_trgm--unpackaged--1.0.sql
/usr/share/postgresql96/extension/pg_trgm.control
/usr/share/postgresql96/extension/pg_visibility--1.0--1.1.sql
/usr/share/postgresql96/extension/pg_visibility--1.1.sql
/usr/share/postgresql96/extension/pg_visibility.control
/usr/share/postgresql96/extension/pgcrypto--1.0--1.1.sql
/usr/share/postgresql96/extension/pgcrypto--1.1--1.2.sql
/usr/share/postgresql96/extension/pgcrypto--1.2--1.3.sql
/usr/share/postgresql96/extension/pgcrypto--1.3.sql
/usr/share/postgresql96/extension/pgcrypto--unpackaged--1.0.sql
/usr/share/postgresql96/extension/pgcrypto.control
/usr/share/postgresql96/extension/pgrowlocks--1.0--1.1.sql
/usr/share/postgresql96/extension/pgrowlocks--1.1--1.2.sql
/usr/share/postgresql96/extension/pgrowlocks--1.2.sql
/usr/share/postgresql96/extension/pgrowlocks--unpackaged--1.0.sql
/usr/share/postgresql96/extension/pgrowlocks.control
/usr/share/postgresql96/extension/pgstattuple--1.0--1.1.sql
/usr/share/postgresql96/extension/pgstattuple--1.1--1.2.sql
/usr/share/postgresql96/extension/pgstattuple--1.2--1.3.sql
/usr/share/postgresql96/extension/pgstattuple--1.3--1.4.sql
/usr/share/postgresql96/extension/pgstattuple--1.4.sql
/usr/share/postgresql96/extension/pgstattuple--unpackaged--1.0.sql
/usr/share/postgresql96/extension/pgstattuple.control
/usr/share/postgresql96/extension/postgres_fdw--1.0.sql
/usr/share/postgresql96/extension/postgres_fdw.control
/usr/share/postgresql96/extension/refint--1.0.sql
/usr/share/postgresql96/extension/refint--unpackaged--1.0.sql
/usr/share/postgresql96/extension/refint.control
/usr/share/postgresql96/extension/seg--1.0--1.1.sql
/usr/share/postgresql96/extension/seg--1.1.sql
/usr/share/postgresql96/extension/seg--unpackaged--1.0.sql
/usr/share/postgresql96/extension/seg.control
/usr/share/postgresql96/extension/sslinfo--1.0--1.1.sql
/usr/share/postgresql96/extension/sslinfo--1.1--1.2.sql
/usr/share/postgresql96/extension/sslinfo--1.2.sql
/usr/share/postgresql96/extension/sslinfo--unpackaged--1.0.sql
/usr/share/postgresql96/extension/sslinfo.control
/usr/share/postgresql96/extension/tablefunc--1.0.sql
/usr/share/postgresql96/extension/tablefunc--unpackaged--1.0.sql
/usr/share/postgresql96/extension/tablefunc.control
/usr/share/postgresql96/extension/tcn--1.0.sql
/usr/share/postgresql96/extension/tcn.control
/usr/share/postgresql96/extension/timetravel--1.0.sql
/usr/share/postgresql96/extension/timetravel--unpackaged--1.0.sql
/usr/share/postgresql96/extension/timetravel.control
/usr/share/postgresql96/extension/tsearch2--1.0.sql
/usr/share/postgresql96/extension/tsearch2--unpackaged--1.0.sql
/usr/share/postgresql96/extension/tsearch2.control
/usr/share/postgresql96/extension/tsm_system_rows--1.0.sql
/usr/share/postgresql96/extension/tsm_system_rows.control
/usr/share/postgresql96/extension/tsm_system_time--1.0.sql
/usr/share/postgresql96/extension/tsm_system_time.control
/usr/share/postgresql96/extension/unaccent--1.0--1.1.sql
/usr/share/postgresql96/extension/unaccent--1.1.sql
/usr/share/postgresql96/extension/unaccent--unpackaged--1.0.sql
/usr/share/postgresql96/extension/unaccent.control
/usr/share/postgresql96/extension/uuid-ossp--1.0--1.1.sql
/usr/share/postgresql96/extension/uuid-ossp--1.1.sql
/usr/share/postgresql96/extension/uuid-ossp--unpackaged--1.0.sql
/usr/share/postgresql96/extension/uuid-ossp.control
/usr/share/postgresql96/extension/xml2--1.0--1.1.sql
/usr/share/postgresql96/extension/xml2--1.1.sql
/usr/share/postgresql96/extension/xml2--unpackaged--1.0.sql
/usr/share/postgresql96/extension/xml2.control
/usr/share/postgresql96/tsearch_data/unaccent.rules
/usr/share/postgresql96/tsearch_data/xsyn_sample.rules


Generated by rpm2html 1.8.1

Fabrice Bellet, Sat Mar 9 12:07:01 2024