Subject: Re: PostgreSQL 13 Beta 1 Release Announcement Draft
To: Alvaro Herrera <alvherre@2ndquadrant.com>,
 "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: PostgreSQL Advocacy <pgsql-advocacy@lists.postgresql.org>
References: <20200520233018.GA32614@alvherre.pgsql>
From: Adrian Klaver <adrian.klaver@aklaver.com>
Message-ID: <f83748bd-b411-562e-2f6c-bf0c7ba15619@aklaver.com>
Date: Wed, 20 May 2020 16:47:44 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <20200520233018.GA32614@alvherre.pgsql>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 5/20/20 4:30 PM, Alvaro Herrera wrote:
> Hello, sorry for the timing on this, but here's some feedback.
> 
> On 2020-May-20, Jonathan S. Katz wrote:
> 

> 
>> One of the most anticipated features of PostgreSQL 13 is the ability for the
>> `VACUUM` command to process indexes in parallel. This functionality can be
>> accessed using the new `PARALLEL` option on the `VACUUM` command (or
>> `--parallel` on `vacuumdb`), which allows you to specify the number of parallel
>> workers to use for vacuuming indexes. Note that this does not work with the
>> `FULL` option.
> 
> I feel this "Note" is unnecessary; VACUUM FULL is of fringe use anyway.

You would hope so, but given the number of times it shows up on 
--general I would say the note is important.

> The phrase on incremental sorting above is better use of these extra
> words, if you have a surplus.
>   

> Thanks!
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com