From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PG 13 release notes, first draft |
Date: | 2020-09-15 15:00:50 |
Message-ID: | e0a4d177-d003-8ebb-5296-5a445472b66f@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/15/20 9:49 AM, Jonathan S. Katz wrote:
> On 9/15/20 5:22 AM, Masahiko Sawada wrote:
>> On Tue, 15 Sep 2020 at 13:56, Peter Eisentraut
>> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>>>
>>> On 2020-09-09 22:57, Jonathan S. Katz wrote:
>>>> + <listitem>
>>>> + <para>
>>>> + Parallelized vacuuming of B-tree indexes
>>>> + </para>
>>>> + </listitem>
>>>
>>> I don't think B-tree indexes are relevant here. AFAICT, this feature
>>> applies to all indexes.
>>>
>>
>> Yes, parallel vacuum applies to all types of indexes provided by
>> PostgreSQL binary, and other types of indexes also can use it.
>
> I'm not sure where I got B-tree from. I've attached a correction.
On a different note, I became aware of this[1] and noticed that dropping
"CREATE EXTENSION ... FROM" was not listed in the incompatibilities
section, so proposing the attached. I have no strong opinions on the
final wording, mainly wanted to get it listed.
Thanks,
Jonathan
Attachment | Content-Type | Size |
---|---|---|
create-extension-from.patch | text/plain | 637 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-09-15 15:45:57 | Re: PG 13 release notes, first draft |
Previous Message | Tom Lane | 2020-09-15 14:59:39 | Re: PG 13 release notes, first draft |