From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | PostgreSQL Advocacy <pgsql-advocacy(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Feature matrix updates |
Date: | 2022-07-19 01:30:37 |
Message-ID: | 2b1f3be3-17ee-10d0-2d11-32d226142c07@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
On 7/17/22 2:53 PM, Peter Geoghegan wrote:
> On Sun, Jul 17, 2022 at 11:34 AM Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
>> In addition to adding information about new features in PostgreSQL
>> 15[1][2], this version of the feature matrix adds additional categories
>> including:
>>
>> * Replication
>> * JSON
>> * Transactions and Visibility
>> * VACUUM and Maintenance
>> * Client Applications
>
> Looks good, but can we remove "Autovacuum enabled by default" and
> "Multiple autovacuum workers"? That would leave only "Integrated
> autovacuum daemon", which seems like it covers the existence of
> autovacuum in enough detail. I believe that autovacuum has existed in
> more or less its current form for far longer than the total lifespan of
> "autovacuum as a contrib extension". Prehistoric autovacuum just
> doesn't seem like a useful point of comparison here.
Yeah, included in the above update was removing some "prehistoric" (as
you term it) features/changes that did not seem to make sense on the matrix.
I think it's OK to remove those two.
> There are still probably some places in the docs which imply that
> autovacuum plays second fiddle to the VACUUM command, when if anything
> it's really the other way around. We still have lots of problems with
> the documentation of VACUUM, which I hope to get around to fixing in
> the next few months.
Sounds good.
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2022-07-19 01:32:34 | Re: Feature matrix updates |
Previous Message | Erik Rijkers | 2022-07-17 20:18:27 | Re: Feature matrix updates |