Movatterモバイル変換


[0]ホーム

URL:



Facebook
Postgres Pro
Facebook
Downloads
E.36. Release 9.5.9
Prev UpAppendix E. Release NotesHome Next

E.36. Release 9.5.9

Release date: 2017-08-31

This release contains a small number of fixes from 9.5.8. For information about new features in the 9.5 major release, seeSection E.45.

E.36.1. Migration to Version 9.5.9

A dump/restore is not required for those running 9.5.X.

However, if you are upgrading from a version earlier than 9.5.8, seeSection E.37.

E.36.2. Changes

  • Show foreign tables ininformation_schema.table_privileges view (Peter Eisentraut)

    All other relevantinformation_schema views include foreign tables, but this one ignored them.

    Since this view definition is installed byinitdb, merely upgrading will not fix the problem. If you need to fix this in an existing installation, you can, as a superuser, do this inpsql:

    SET search_path TO information_schema;CREATE OR REPLACE VIEW table_privileges AS    SELECT CAST(u_grantor.rolname AS sql_identifier) AS grantor,           CAST(grantee.rolname AS sql_identifier) AS grantee,           CAST(current_database() AS sql_identifier) AS table_catalog,           CAST(nc.nspname AS sql_identifier) AS table_schema,           CAST(c.relname AS sql_identifier) AS table_name,           CAST(c.prtype AS character_data) AS privilege_type,           CAST(             CASE WHEN                  -- object owner always has grant options                  pg_has_role(grantee.oid, c.relowner, 'USAGE')                  OR c.grantable                  THEN 'YES' ELSE 'NO' END AS yes_or_no) AS is_grantable,           CAST(CASE WHEN c.prtype = 'SELECT' THEN 'YES' ELSE 'NO' END AS yes_or_no) AS with_hierarchy    FROM (            SELECT oid, relname, relnamespace, relkind, relowner, (aclexplode(coalesce(relacl, acldefault('r', relowner)))).* FROM pg_class         ) AS c (oid, relname, relnamespace, relkind, relowner, grantor, grantee, prtype, grantable),         pg_namespace nc,         pg_authid u_grantor,         (           SELECT oid, rolname FROM pg_authid           UNION ALL           SELECT 0::oid, 'PUBLIC'         ) AS grantee (oid, rolname)    WHERE c.relnamespace = nc.oid          AND c.relkind IN ('r', 'v', 'f')          AND c.grantee = grantee.oid          AND c.grantor = u_grantor.oid          AND c.prtype IN ('INSERT', 'SELECT', 'UPDATE', 'DELETE', 'TRUNCATE', 'REFERENCES', 'TRIGGER')          AND (pg_has_role(u_grantor.oid, 'USAGE')               OR pg_has_role(grantee.oid, 'USAGE')               OR grantee.rolname = 'PUBLIC');

    This must be repeated in each database to be fixed, includingtemplate0.

  • Clean up handling of a fatal exit (e.g., due to receipt ofSIGTERM) that occurs while trying to execute aROLLBACK of a failed transaction (Tom Lane)

    This situation could result in an assertion failure. In production builds, the exit would still occur, but it would log an unexpected message aboutcannot drop active portal.

  • Remove assertion that could trigger during a fatal exit (Tom Lane)

  • Correctly identify columns that are of a range type or domain type over a composite type or domain type being searched for (Tom Lane)

    CertainALTER commands that change the definition of a composite type or domain type are supposed to fail if there are any stored values of that type in the database, because they lack the infrastructure needed to update or check such values. Previously, these checks could miss relevant values that are wrapped inside range types or sub-domains, possibly allowing the database to become inconsistent.

  • Fix crash inpg_restore when using parallel mode and using a list file to select a subset of items to restore (Fabrízio de Royes Mello)

  • Changeecpg's parser to allowRETURNING clauses without attached C variables (Michael Meskes)

    This allowsecpg programs to contain SQL constructs that useRETURNING internally (for example, inside a CTE) rather than using it to define values to be returned to the client.

  • Improve selection of compiler flags for PL/Perl on Windows (Tom Lane)

    This fix avoids possible crashes of PL/Perl due to inconsistent assumptions about the width oftime_t values. A side-effect that may be visible to extension developers is that_USE_32BIT_TIME_T is no longer defined globally inPostgreSQL Windows builds. This is not expected to cause problems, because typetime_t is not used in anyPostgreSQL API definitions.

  • Fixmake check to behave correctly when invoked via a non-GNU make program (Thomas Munro)


Prev Up Next
E.35. Release 9.5.10 Home E.37. Release 9.5.8
pdfepub
Go to Postgres Pro Standard 9.5
By continuing to browse this website, you agree to the use of cookies. Go toPrivacy Policy.

[8]ページ先頭

©2009-2025 Movatter.jp