Hi Bruce, On Wed, Apr 15, 2026 at 9:19 AM Bruce Momjian <bruce@momjian.us> wrote: > > I have completed the first draft of the PG 19 release notes: > > https://www.postgresql.org/docs/devel/release-19.html > > The feature count is 212. The recent average is 200: > > https://momjian.us/main/writings/pgsql/missing.pdf#page=3 > > I will create a wiki page to explain my methods used to create this > because, someday, someone else will need to do this. > > I am traveling April 19 to May 7, so I might not be able to make quick > adjustments based on feedback. Another committer can handle them, or > you can wait for me to get to it. Thanks for working on the draft. Here're some comments for it: 1) Improve performance of pgstattuple by using streaming reads There are two related commits that improve the performance of pgstattuple. The current hyperlink references [1]; would it make sense to include [2] too? [1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=213f0079b [2] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=ae58189a4d523f0156ebe30f4534180555669e88 2) Additionally, would this[3] be something worth mentioning in the General Performance section? The improvement looks fairly big. [3] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=6c228755add8f0714677440d53a160f9ed332902 3) Allow standbys to wait for LSN values to be replayed via WAIT FOR As for this feature, the follow-up commit[4] extends the WAIT FOR command to support waiting for flush and write operations. Is it helpful for users to be aware of these use cases as well? [4] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=49a181b5d634340fcfb7c762c387c03f6405367e Thanks! -- Best, Xuneng
pgsql-hackers by date:
Соглашаюсь с условиями обработки персональных данных