On Fri, 6 Sept 2024 at 19:04, Jonathan S. Katz <jk...@postgresql.org> wrote: > > On 9/4/24 5:04 PM, Jonathan S. Katz wrote: > > Hi, > > > > Attached is the draft of the PostgreSQL 17 release announcement. This is > > a draft of the text that will go into the press kit, with the key > > portions to review starting from the top of the document, up until the > > "About PostgreSQL" section. > > > > Please provide feedback on content accuracy, notable omissions or items > > that should be excluded, or if an explanation is unclear and needs > > better phrasing. On the last point, I'm looking to ensure the wording is > > clear and is easy to translate into different languages. > > > > Based on feedback, I'll be posting a revision once a day (if there's > > feedback) until the review cut-off. We'll have to freeze the > > announcement by Mon, Sep 9 @ 12:00 UTC so we can begin the translation > > process. > > > > Thank you for your help with the release process! > > Please see v2 attached. As per original note, please provide feedback > before Mon, Sep 9 @ 12:00 UTC so we can begin the translation process.
> [`EXPLAIN`](...) now shows the time spent for I/O block reads and writes I think this needs some adjustment: IIUC the new feature in PG17's 295c36c0 is that we now also track (and show) timings for local blocks. I/O timings on shared and temp blocks were already tracked (and displayed with the BUFFERS option) when track_io_timing was enabled: temp timing was introduced with efb0ef90 in early April 2022, and the output of IO timings for shared blocks has existed since the introduction of track_io_timing in 40b9b957 back in late March of 2012. Kind regards, Matthias van de Meent
