Re: First draft of back-branch release notes is done - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: First draft of back-branch release notes is done
Date
Msg-id 20230208220835.GN1653@telsasoft.com
Whole thread Raw
In response to First draft of back-branch release notes is done  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: First draft of back-branch release notes is done
List pgsql-hackers
On Fri, Feb 03, 2023 at 02:32:39PM -0500, Tom Lane wrote:
> ... at
> 
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=f282b026787da69d88a35404cf62f1cc21cfbb7c
> 
> As usual, please send corrections/comments by Sunday.

It's of no concern, but I was curious why this one wasn't included:

commit 72aea955d49712a17c08748aa9abcbcf98c32fc5
Author: Thomas Munro <tmunro@postgresql.org>
Date:   Fri Jan 6 16:38:46 2023 +1300

    Fix pg_truncate() on Windows.
    
    Commit 57faaf376 added pg_truncate(const char *path, off_t length), but
    "length" was ignored under WIN32 and the file was unconditionally
    truncated to 0.
    
    There was no live bug, since the only caller passes 0.
    
    Fix, and back-patch to 14 where the function arrived.



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: WAL Insertion Lock Improvements
Next
From: Andrew Dunstan
Date:
Subject: Re: run pgindent on a regular basis / scripted manner