| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PG 14 release notes, first draft |
| Date: | 2021-05-12 19:48:14 |
| Message-ID: | 20210512194814.GM6088@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 11, 2021 at 05:47:27PM -0400, Álvaro Herrera wrote:
> On 2021-May-11, Bruce Momjian wrote:
>
> > > 86dc90056d Rework planning and execution of UPDATE and DELETE.
> > > a1115fa078 Postpone some more stuff out of ExecInitModifyTable.
> > > c5b7ba4e67 Postpone some stuff out of ExecInitModifyTable.
>
> Are these the set that means UPDATE/DELETE can now do partition pruning?
> I think that's a significant improvement, because table partitioning
> becomes usable in situations where it previously wasn't, so let's
> mention it.
>
> > > c7aba7c14e Support subscripting of arbitrary types, not only arrays.
>
> There's an entry that says we allow subscripting of jsonb, but the
> feature is more general than that: our subscripting is now extensible,
> and jsonb is just the first implementation. I think this should be
> mentioned.
OK, I added it into the existing entry:
<listitem>
<!--
Author: Alexander Korotkov <akorotkov(at)postgresql(dot)org>
2021-01-31 [676887a3b] Implementation of subscripting for jsonb
Author: Alexander Korotkov <akorotkov(at)postgresql(dot)org>
2021-01-31 [81fcc72e6] Filling array gaps during jsonb subscripting
Author: Alexander Korotkov <akorotkov(at)postgresql(dot)org>
2021-01-31 [aa6e46daf] Throw error when assigning jsonb scalar instead of a com
-->
<para>
Allow subscripting of jsonb (Dmitry Dolgov)
</para>
<para>
Subscripting can be used to extract from and assign to jsonb documents.
Subscripting is now extensible so extensions and built-in data type can make use of this.
</para>
</listitem>
> > > f40c6969d0 Routine usage information schema tables
>
> This is one small step towards compliance, I think, so it should be
> mentioned.
I added this item:
<listitem>
<!--
Author: Peter Eisentraut <peter(at)eisentraut(dot)org>
2021-02-17 [f40c6969d] Routine usage information schema tables
-->
<para>
Implement information schema view routine_column_usage to track columns
referenced by function and procedure default expressions (Peter Eisentraut)
</para>
</listitem>
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-05-12 19:58:57 | Re: Granting control of SUSET gucs to non-superusers |
| Previous Message | Andres Freund | 2021-05-12 19:34:12 | Re: Always bump PG_CONTROL_VERSION? |