On Sat, 3 Jun 2023 at 00:14, Jonathan S. Katz <jkatz@xxxxxxxxxxxxxx> wrote: > Typically once a release announcement is out, we'll only edit it if it's > inaccurate. I don't think the statement in the release announcement is > inaccurate, as it specifies that concurrent bulk loading is faster. Understood. I had thought that the policy might be that if there's room for and reason enough to make improvements, then we probably should. We do aim to still make improvements to fix any problem with the software that's the topic of the announcement, maybe it's strange that we want to lock down what we write about that software just before the beta1 release. > I'm -0.5 for revising the announcement, but I also don't want people to > miss out on testing this. I'd be OK with this: > > "PostgreSQL 16 can also improve the performance of bulk loading of data, > with some tests showing using up to 300% improvement when concurrently > executing `COPY` commands." I might have just misunderstood the release notes based on my misunderstanding of Andres's work that it only improved things when multiple backends were extending the relation at the same time. The release announcement did seem to confirm that there had to be concurrency, so it might be good to not lead anyone else down into thinking that only concurrent cases are faster. I certainly understand that's where the big wins are. I'm fine with your proposed wording. David
