From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | "PostgreSQL Advocacy Group (pgsql-advocacy(at)postgresql(dot)org)" <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL 11 Major Features |
Date: | 2018-06-08 14:26:25 |
Message-ID: | B1A56825-8CEC-4270-9FC1-EC0BD17D7266@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
> On May 24, 2018, at 10:48 AM, Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
>
> Hi,
>
> PostgreSQL 11 Beta 1 went live today with a preliminary list of major
> features:
>
> https://www.postgresql.org/docs/11/static/release-11.html#id-1.11.6.5.3 <https://www.postgresql.org/docs/11/static/release-11.html#id-1.11.6.5.3>
>
> As with everything in the beta, this may not be the final list: we may
> need to add / remove based on what we see in testing, what features
> may have more of an impact on people’s usage of PostgreSQL than
> we may have initially noticed, etc.
>
> I wanted to start this thread not to both facilitate a discussion of what
> the major features are going into PostgreSQL 11 and as a means to
> collect user feedback from beta testing to see if there is something we
> should be highlighting that we are not (or something we shouldn’t
> highlight).
>
> So, please encourage people to test the PostgreSQL 11 beta and
> provide feedback so we can effectively message the release come
> the fall!
So one I would suggest adding is “covering indexes” - they seem like
they could be very helpful[1].
Jonathan
[1] https://paquier.xyz/postgresql-2/postgres-11-covering-indexes/ <https://paquier.xyz/postgresql-2/postgres-11-covering-indexes/>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-06-08 15:57:47 | Re: Code of Conduct plan |
Previous Message | Jonathan S. Katz | 2018-06-08 12:19:26 | Re: Code of Conduct plan |