Horton

Re: PG 14 release notes, first draft

Simon Riggs <simon.riggs@enterprisedb.com>

View thread View on postgr.es
From: Simon Riggs <simon.riggs@enterprisedb.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Peter Geoghegan <pg@bowt.ie>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-07-01T14:13:30Z
Lists: pgsql-hackers 
On Wed, Jun 30, 2021 at 11:20 PM Bruce Momjian <bruce@momjian.us> wrote:
>
> On Tue, Jun 29, 2021 at 07:36:47PM +0100, Simon Riggs wrote:
> > Perhaps we should also add this text from the commit message to ensure
> > the importance is understood:
> > "This is extremely useful in cases where CIC/RC can run for a very long
> >     time, because that used to be a significant headache for concurrent
> >     vacuuming of other tables."
>
> Uh, hopefully this idea is captured below.
>
> > Proposed edits:
> >
> > * "during certain index operations" -> "while concurrent index
> > operations run on other tables"
>
> Uh, the problem here is that it isn't clear if we are talking about
> concurrent index operations, "concurrently"-enabled index options, or
> "concurrently"-enabled concurrent index operations.  I went with
> "minimal-locking index operations".
>
> > * spell Alvaro's name correctly
>
> Uh, this is the second time Mutt's default to using iso-8859-1 for
> non-ASCII attachments has caused confusion.  I found that using 'set
> send_charset="us-ascii:utf-8"' in Mutt fixed this, so the attachment
> should now be fine.
>
> > * "row expiration" is a term not currently used in PG docs, so we
> > should probably look for something else.
>
> Yeah, I changed that to "removing dead rows" which seems to be our
> standard text.

What you have now looks great for this feature, thanks.


> > There are 2 important features here, so the 2nd feature is worth
> > mentioning also:
> >
> > Avoid spurious waits in concurrent indexing
> >
> > Previously, multiple concurrent index operations could deadlock or
> > cause long waits.
> > Waits are avoided except for indexes with expressions, or WHERE predicates.
>
> OK, I added text to the bottom to try and capture that;  new patch
> attached, now with UTF8 encoding.

The text from "This also avoids..." tries to explain this, but they
are two separate features, each important in its own right.

So regrettably, this part doesn't capture it, for me.

-- 
Simon Riggs                http://www.EnterpriseDB.com/

Commits

  1. doc: add mention of +4GB windows file handling in PG14 relnotes

  2. doc: PG 14 relnotes fixes

  3. doc: PG 14 relnote updates

  4. doc: PG 14 relnotes, adjust pg_{read|write}_all_data entry

  5. Update PG 14 relnotes for vacuum_cost_page_miss

  6. doc: update PG 14 release notes with recent feedback

  7. Update replication statistics after every stream/spill.

  8. Add information of total data processed to replication slot stats.

  9. Use NameData datatype for slotname in stats.

  10. Add back vacuum_cleanup_index_scale_factor parameter.

  11. Don't consider newly inserted tuples in nbtree VACUUM.

  12. pgbench: Improve time logic.

  13. Track total amounts of times spent writing and syncing WAL data to disk.

  14. Allow decoding at prepare time in ReorderBuffer.

  15. Extend the output plugin API to allow decoding of prepared xacts.

  16. Fix nbtree cleanup-only VACUUM stats inaccuracies.

  17. Execute invalidation messages for each XLOG_XACT_INVALIDATIONS message

  18. Fix our Windows stat() emulation to handle file sizes > 4GB.

  19. Trigger autovacuum based on number of INSERTs

  20. Speed up planning when partitions can be pruned at plan time.

  21. Remove support for password_encryption='off' / 'plain'.

  22. Increase work_mem and maintenance_work_mem defaults by 4x