⭐ psql: save/restore truePrint/falsePrint printQueryOpt values
Author: Bruce Momjian — Discussion: 83e247ed-0b2d-4aba-bc42-e7bbc20be0d6@postgrespro.ru
This commit addresses an issue in psql where the truePrint and falsePrint options were not being correctly saved and restored, as reported by A. Kozhemyakin. This ensures consistent behavior when these printing options are used.
doc PG 19 relnotes: add two optimizer hooks
Author: Bruce Momjian — Discussion: CACJufxE8Ew_DCXtd1VZSC=pNPHqZRa4RJkbCr7z6ZPJJ3o3hGQ@mail.gmail.com
This documentation commit adds information about two new optimizer hooks to the PostgreSQL 19 release notes, as reported by Jian He. These hooks provide new extension points for query optimization.
De-obfuscate the comment in tsrank.c's calc_rank_or().
Author: Tom Lane
This commit replaces an obscure comment in tsrank.c with a clearer explanation, reverse-engineered by Aleksander Alekseev. It also reorders the final expression to match the new comment, improving code readability and maintainability.
doc PG 19 relnotes: remove "Optionally" for CPU optimizations
Author: Bruce Momjian — Discussion: CANWCAZZWfdoMcemSaTMon+e6aCkSABN3+sco0aStC90cFPVE4A@mail.gmail.com
This commit refines the PostgreSQL 19 release notes by removing the word "Optionally" regarding CPU optimizations, as reported by John Naylor. This clarification improves the accuracy of the documentation.
⭐ Add psql tab completion for FOR PORTION OF clause
Author: Peter Eisentraut — Discussion: CAD0dvCQLqLzPrQJRjjA2qXDH%3DD%2BXShcxhbSPxNhVruC8HGhkbQ%40mail.gmail.com
This commit introduces tab completion support in psql for the FOR PORTION OF clause used with UPDATE and DELETE statements on temporal tables. This enhancement guides users through the syntax, making it easier to construct queries.
Why it matters: This new feature significantly improves the user experience for developers and operators working with temporal tables in psql, reducing the need to remember precise syntax.
pg_stat_statements: Fix potential use-after-free of PlannedStmt
Author: Michael Paquier
This commit fixes a critical use-after-free bug in pg_stat_statements that could occur due to an incorrect memory access related to PlannedStmt data. The fix addresses a scenario where the PlannedStmt could be freed prematurely, especially when using the extended query protocol with internal rollback queries.
HN News
⭐ Snowflake Postgres, Lakebase, HorizonDB: Picking the Lock-In You Want
Score: 17 / Comments: 4
This article discusses the various PostgreSQL-compatible database services and their implications for vendor lock-in. It explores how choices like Snowflake Postgres, Lakebase, and HorizonDB present different trade-offs for developers and operators in terms of flexibility and ecosystem integration.
Summary
Today's PostgreSQL news includes a useful new psql tab completion feature for temporal table operations and a critical bug fix in pg_stat_statements addressing a use-after-free vulnerability. Additionally, an insightful Hacker News article sparked discussion on vendor lock-in when choosing PostgreSQL-based database services.
This digest was generated by gemini based on Hacker News, GitHub, and the PostgreSQL mailing list.