pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: Josh Berkus <josh@berkus.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Catching up with performance & PostgreSQL 15
Date: Mon, 28 Nov 2022 21:34:58 -0600
Message-ID: <20221129033458.GF11463@telsasoft.com> (raw)
In-Reply-To: <89e7da59-0dfe-45fe-e082-00f777e200a1@berkus.org>
References: <89e7da59-0dfe-45fe-e082-00f777e200a1@berkus.org>

On Mon, Nov 28, 2022 at 06:59:41PM -0800, Josh Berkus wrote:
> Hey, folks:
> 
> I haven't configured a PostgreSQL server since version 11 (before that, I
> did quite a few).
> 
> What's changed in terms of performance configuration since then?  Have the
> fundamentals of shared_buffers/work_mem/max_connections changed at all?
> Which new settings are must-tunes?
> 
> I've heard about new parallel stuff an JIT, but neither is that applicable
> to my use-case.

shared buffers is the same, but btree indexes are frequently (IME) 3x
smaller (!) since deduplication was added in v13, so s_b might not need
to be as large.

In addition to setting work_mem, you can also (since v13) set
hash_mem_multiplier.

default_toast_compression = lz4 # v14
recovery_init_sync_method = syncfs # v14
check_client_connection_interval = ... # v14
wal_compression = {lz4,zstd} # v15

Peeking at my notes, there's also: partitioning, parallel query, brin
indexes, extended statistics, reindex concurrently, ...

... but I don't think anything is radically changed :)

-- 
Justin





view thread (17+ messages)  latest in thread

Message-ID: <20221129033458.GF11463@telsasoft.com>
Permalink:  ../20221129033458.GF11463@telsasoft.com/
Also on:    postgresql.org/message-id/20221129033458.GF11463@telsasoft.com

 · 

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: pgsql-performance@postgresql.org
  Cc: pryzby@telsasoft.com, josh@berkus.org
  Subject: Re: Catching up with performance & PostgreSQL 15
  In-Reply-To: <20221129033458.GF11463@telsasoft.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox