| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: First draft of the PG 15 release notes |
| Date: | 2022-05-24 23:36:00 |
| Message-ID: | Yo1r4IKRnFUgWlPy@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 19, 2022 at 06:13:28PM +0900, Amit Langote wrote:
> Or maybe we could mention that but use a wording that doesn't make it
> sound like an implementation detail, like:
>
> +Previously, an ordered partition scan could not be used for a
> LIST-partitioned table with any partition containing multiple values,
> nor for partitioned tables with DEFAULT partition. Now it can be used
> in those cases at least for queries in which such partitions are
> pruned.
Sorry, I just don't see this as an improvement because it starts with a
complex term "an ordered partition scan" rather than simply "a
partitioned table".
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-05-24 23:40:45 | Re: Limiting memory allocation |
| Previous Message | Bruce Momjian | 2022-05-24 23:31:56 | Re: First draft of the PG 15 release notes |