From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Josh Berkus <josh(at)berkus(dot)org> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Catching up with performance & PostgreSQL 15 |
Date: | 2022-11-29 03:34:58 |
Message-ID: | 20221129033458.GF11463@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Mladen Gogala | 2022-11-29 03:39:47 | Re: Catching up with performance & PostgreSQL 15 |
Previous Message | Josh Berkus | 2022-11-29 02:59:41 | Catching up with performance & PostgreSQL 15 |