Jump to:
Config parameter: | Default value: |
---|---|
default_with_oids | off |
force_parallel_mode | off |
operator_precedence_warning | off |
stats_temp_directory | pg_stat_tmp |
vacuum_cleanup_index_scale_factor | 0.1 |
vacuum_defer_cleanup_age | 0 |
wal_keep_segments | 0 |
Config parameter: | Default value in Pg 11: | Default value in Pg 16: |
---|---|---|
autovacuum_vacuum_cost_delay | 20 | 2 |
checkpoint_completion_target | 0.5 | 0.9 |
extra_float_digits | 0 | 1 |
jit | off | on |
log_autovacuum_min_duration | -1 | 600000 |
log_checkpoints | off | on |
password_encryption | md5 | scram-sha-256 |
vacuum_cost_page_miss | 10 | 2 |
⇑ Upgrade to 14 released on 2021-09-30 - docs
Add executor method to memoize results from the inner side of a nested-loop join (David Rowley)
This is useful if only a small percentage of rows is checked on the inner side. It can be disabled via server parameter enable_memoize.
⇑ Upgrade to 14.1 released on 2021-11-11 - docs
Avoid choosing the wrong hash equality operator for Memoize plans (David Rowley)
This error could result in crashes or incorrect query results.
⇑ Upgrade to 14.2 released on 2022-02-10 - docs
Fix Memoize plan nodes to handle subplans that use parameters coming from above the Memoize (David Rowley)
Fix Memoize plan nodes to work correctly with non-hashable join operators (David Rowley)
⇑ Upgrade to 14.4 released on 2022-06-16 - docs
Harden Memoize plan node against non-deterministic equality functions (David Rowley)
Memoize could crash if a data type's equality or hash functions gave inconsistent results across different calls. Throw a runtime error instead.
Fix incorrect cost estimates for Memoize plans (David Rowley)
This mistake could lead to Memoize being used when it isn't really the best plan, or to very long executor startup times due to initializing an overly-large hash table for a Memoize node.
⇑ Upgrade to 15.2 released on 2023-02-09 - docs
Fix planner issues when combining Memoize nodes with partitionwise joins or parameterized nestloops (Richard Guo)
These errors could lead to not using Memoize in contexts where it would be useful, or possibly to wrong query plans.
⇑ Upgrade to 15.3 released on 2023-05-11 - docs
Fix memory leak in Memoize plan execution (David Rowley)
⇑ Upgrade to 15.4 released on 2023-08-10 - docs
Don't Memoize lateral joins with volatile join conditions (Richard Guo)
Applying Memoize to a sub-plan that contains volatile filter conditions is likely to lead to wrong answers. The check to avoid doing this missed some cases that can arise when using LATERAL
.
⇑ Upgrade to 16 released on 2023-09-14 - docs
Allow memoize atop a UNION ALL
(Richard Guo)