public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jonathan S. Katz <[email protected]>
To: Peter Geoghegan <[email protected]>
Cc: PostgreSQL Advocacy <[email protected]>
Subject: Re: Feature matrix updates
Date: Mon, 18 Jul 2022 21:30:37 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAH2-WzkF8NqSLtibpcq5R8NE_8Ms=dt=MvJzEN=5jTvZDWNZKQ@mail.gmail.com>
References: <[email protected]>
<CAH2-WzkF8NqSLtibpcq5R8NE_8Ms=dt=MvJzEN=5jTvZDWNZKQ@mail.gmail.com>
On 7/17/22 2:53 PM, Peter Geoghegan wrote:
> On Sun, Jul 17, 2022 at 11:34 AM Jonathan S. Katz <[email protected]> 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
Attachments:
[application/pgp-signature] OpenPGP_signature (840B, 2-OpenPGP_signature)
download
view thread (7+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Feature matrix updates
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox