![]() ![]() Support wal_sync_method=fdatasync on Windows (Thomas Munro)Īllow HOT updates if only BRIN-indexed columns are updated (Matthias van de Meent, Josef Simanek, Tomas Vondra) The default value is set by server variable vacuum_buffer_usage_limit, which also controls autovacuum. The VACUUM/ ANALYZE option is BUFFER_USAGE_LIMIT, and the vacuumdb option is -buffer-usage-limit. Improve performance by caching RANGE and LIST partition lookups (Amit Langote, Hou Zhijie, David Rowley)Īllow control of the shared buffer usage by vacuum and analyze (Melanie Plageman) This makes full-table freeze vacuums less necessary.Īllow window functions to use the faster ROWS mode internally when RANGE mode is active but unnecessary (David Rowley)Īllow optimization of always-increasing window functions ntile(), cume_dist() and percent_rank() (David Rowley)Īllow aggregate functions string_agg() and array_agg() to be parallelized (David Rowley) Remove symbolic links for the postmaster binary (Peter Eisentraut)Īllow more efficient addition of heap and index pages (Andres Freund)ĭuring non-freeze operations, perform page freezing where appropriate (Peter Geoghegan) ![]() For example, they can now change the CREATEDB, REPLICATION, and BYPASSRLS properties only if they also have those permissions. Such changes, including adding members, now require the role requesting the change to have ADMIN OPTION permission. Previously roles with CREATEROLE privileges could change many aspects of any non-superuser role. Restrict the privileges of CREATEROLE and its ability to modify other roles (Robert Haas) Previously the inheritance status of member roles was controlled only by the role's inheritance status, and changes to a role's inheritance status affected all previous and future member roles. This allows inheritance of some roles and not others because the members' inheritance status is set at GRANT time. The role's default inheritance behavior can be overridden with the new GRANT. Role inheritance now controls the default inheritance status of member roles added during GRANT (Robert Haas) Remove read-only server variables lc_collate and lc_ctype (Peter Eisentraut)Ĭollations and locales can vary between databases so having them as read-only server variables was unhelpful. This was used to promote a standby to primary, but is now more easily accomplished with pg_ctl promote or pg_promote(). Remove server variable promote_trigger_file (Simon Riggs) This has been unnecessary since hot_standby_feedback and replication slots were added. Remove the server variable vacuum_defer_cleanup_age (Andres Freund) Remove the ability to create views manually with ON SELECT rules (Tom Lane) Rename server variable force_parallel_mode to debug_parallel_query (David Rowley) Remove pg_walinspect functions pg_get_wal_records_info_till_end_of_wal() and pg_get_wal_stats_till_end_of_wal() (Bharath Rupireddy) Tighten GENERATED expression restrictions on inherited and partitioned tables (Amit Langote, Tom Lane)Ĭolumns of parent/partitioned and child/partition tables must all have the same generation status, though now the actual generation expressions can be different. Processing such indexes is still possible using REINDEX SYSTEM and reindexdb -system. ![]() To restore the previous behavior, assign the desired portal name to the cursor variable before OPEN.ĭisallow NULLS NOT DISTINCT indexes for primary keys (Daniel Gustafsson)Ĭhange REINDEX DATABASE and reindexdb to not process indexes on system catalogs (Simon Riggs) Previously, the string value of such variables was set to match the variable name during cursor assignment now it will be assigned during OPEN, and will not match the variable name. Change assignment rules for PL/pgSQL bound cursor variables (Tom Lane)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |