Re: Release 14 Schedule

On Wed, Sep 22, 2021 at 6:30 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
> > On 9/22/21 11:15 AM, Magnus Hagander wrote:
> >> On Wed, Sep 22, 2021 at 5:12 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >>> Numerous performance improvements have been made for parallel queries,
> >>> heavily-concurrent workloads, partitioned tables, logical replication, and
> >>> vacuuming. Notably, foreign data wrappers can now make use of query
> >>> parallelism.
>
> >> "foreign data wrappers and stored procedures/functions" maybe?
>
> > +1
>
> I thought the point about FDWs was important because actual work (by
> FDW authors) is needed to make anything happen. The extra parallelism
> inside plpgsql functions doesn't require user effort, so I don't see
> that it needs to be called out separately.

True, but I'm willing to guess we have a lot more people who are using
stored procs with return query and who are going to be very happy
about them now being much faster in cases where parallelism worked,
than we have people who are writing FDWs..

That said, I'm not suggesting we remove the mention of the FDWs, just
that we keep both.

> >> I have a feeling emergency mode vacuum fits on that list. Not in the
> >> press release, but in the major features list of the release notes.
>
> > Given some recent news I saw floating around, I'd agree with this.
>
> Meh ... if it didn't make the press release's longer list, why is
> it critical here?

My take on that is audience. It's an important feature for existing
users of PostgreSQL, and an important change over how the system
behaved before. They are more likely to read the release notes. The
press release is more about reaching people who are not already using
postgres, or who are so but more tangentially.

Maybe that audience take is wrong though, but it is what I based the idea on :)

--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/