Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ligyd-00038H-N3 for pgsql-advocacy@arkaria.postgresql.org; Mon, 17 May 2021 17:24:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ligyb-0006I8-0g for pgsql-advocacy@arkaria.postgresql.org; Mon, 17 May 2021 17:24:21 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ligya-0006Fp-KS for pgsql-advocacy@lists.postgresql.org; Mon, 17 May 2021 17:24:20 +0000 Received: from mail-oi1-x229.google.com ([2607:f8b0:4864:20::229]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ligyT-0003u7-D4 for pgsql-advocacy@lists.postgresql.org; Mon, 17 May 2021 17:24:19 +0000 Received: by mail-oi1-x229.google.com with SMTP id f184so7184988oig.3 for ; Mon, 17 May 2021 10:24:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=ybEgcFVyQ5NAS+HW1ETQ6jKQ4yfigial3023kpPOL2E=; b=mtpqsU3GIc9DCzvyLxr+iHC0dmEA6vXh4Y/pbtEDzI7e8+4sdSsTBewgwWkK0SACX6 7htqhqUoaFWE4a/g6BnPHOALd+JD/ya+VGKmXHcKezb4jucKs2nBlgZIVr+A/abhCrrK pdZTYB3pZ0wPkeL41b6ZqBxfXLVQUCu4s0WsBCMbdI4K3ftRIIFicNn0oV5IA7YHbDUY wfsbm4MZrgnaBok9fyDGwFgMmvSYaa2tpbSr2XXZzC6fHZScZeb/rfytRSdtwjrw6SI3 fNByxId6ZkDO+fbxoXZiRQaBn8SjvcHHyrX5g+dd0bBUHtZIr5fh577ao/NS3xpQEyj9 Hd1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ybEgcFVyQ5NAS+HW1ETQ6jKQ4yfigial3023kpPOL2E=; b=UH+yfRrjII/8RHaUYixb9SJKuLGMS5cVS1evSdGFNOcIk+EXcaNfj5mBphaOn8Q1Lf 9s2K+bq8mCLi/aNogJWYp4yd/Bvy0KvV/gsZhzlR8M8YL3Nm+z7fVvjLs7dH3m+xA03G DD6pffl6hDcU+/ap7qROfoytQX3ybtdUi3gNepN8dVZNDSAGNSim0vFtwn71RqfZYIc7 +P+IC7ksG620KKfoyCxoSBXNqTH6MYRVtEkCTEihTIs/TxwHHu7wdq1rsLLe200ZpSrx t1WOi1k7NzqfY3B+OaKLXV87IO91drfywh1q+p+YkEimTXLoBlf4hUC/dDeE1GmYDDYf BboA== X-Gm-Message-State: AOAM530kqo+Hremj14LYm28deERawFQnyaSiez7dKheN1vf1EjR23BRl 3IN7htMigbB9AyAauWqrQZgjBB+bn9Z32w== X-Google-Smtp-Source: ABdhPJyh6lNrZMBEcY9u4xZ3A5C1VnfOPgUTVymX5a16/WqRae7gjpukQ1uAr8dG/ycsuq+/W6n4zA== X-Received: by 2002:a05:6808:13cb:: with SMTP id d11mr156046oiw.138.1621272252043; Mon, 17 May 2021 10:24:12 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id y7sm3245693oto.60.2021.05.17.10.24.11 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 May 2021 10:24:11 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 8C232800870; Mon, 17 May 2021 12:24:10 -0500 (CDT) Date: Mon, 17 May 2021 12:24:10 -0500 From: Justin Pryzby To: "Jonathan S. Katz" Cc: pgsql-advocacy@lists.postgresql.org Subject: Re: PostgreSQL 14 Beta 1 release announcement draft Message-ID: <20210517172410.GH373@telsasoft.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, May 17, 2021 at 10:15:56AM -0400, Jonathan S. Katz wrote: > This release has significant improvements in transaction throughput in > PostgreSQL systems that have large numbers of connections to the database, > regardless if they are active or idle. regardless of whether (I think) > indexes. [GiST indexes](https://www.postgresql.org/docs/14/indexes-types.html#INDEXES-TYPE-GIST) > can now use pre-sorted data during their build process, allowing both for faster > index creation and smaller indexes. Instead of "use pre-sorted" I think it should say "can now pre-sort.." > [SP-GiST indexes](https://www.postgresql.org/docs/14/indexes-types.html#INDEXES-TYPE-SPGIST) > now support [covering indexes](https://www.postgresql.org/docs/14/indexes-index-only-scans.html) > that allow users to add additional, nonsearchable columns to the index through > the `INCLUDE` clause. *in the index > PostgreSQL 14. This new release adds more capabilities to [extended statistics](https://www.postgresql.org/docs/14/planner-stats.html), > which can now be used on [expressions](https://www.postgresql.org/docs/14/view-pg-stats-ext-exprs.html). can be *created on expressions > PostgreSQL has supported compression on its "oversized data" columns (i.e. the > [TOAST](https://www.postgresql.org/docs/14/storage-toast.html) system) for > decades, but this release adds the ability to now choose to use > [LZ4 compression](https://www.postgresql.org/docs/14/sql-createtable.html) on > tables. say "on TOAST tables", otherwise it sounds like what's new is "tables" rather than "LZ4". > PostgreSQL 14 includes numerous improvements on what information can be > monitored, including the ability to track progress on `COPY` using the > [`pg_stat_progress_copy`](https://www.postgresql.org/docs/14/progress-reporting.html#COPY-PROGRESS-REPORTING) > view. This release lets WAL activity be tracked from the [`pg_stat_wal`](https://www.postgresql.org/docs/14/monitoring-stats.html#MONITORING-PG-STAT-WAL-VIEW) "allows WAL activity to be tracked" > The [`REINDEX`](https://www.postgresql.org/docs/14/sql-reindex.html) command in in *PostgreSQL 14 > of waiting for them to be completed. The [`ALTER SUBSCRIPTION`](https://www.postgresql.org/docs/14/sql-altersubscription.html) > makes it easier to add/remove publications using the new `ADD/DROP PUBLICATION`] > syntax. missing "command" > PostgreSQL 14 now adds a general subscripting framework for retrieving remove "now" As usual, Erik already reported half of my typos ;) -- Justin