Doc: Improve documentation for pg_jit_available()
Per complaint from Scott Ribe. Based on wording suggestion from Tom Lane.
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 11, where pg_jit_available() was added
Branch
--
REL_11_STABLE
Doc: Improve documentation for pg_jit_available()
Per complaint from Scott Ribe. Based on wording suggestion from Tom Lane.
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 11, where pg_jit_available() was added
Branch
--
REL_12_STABLE
Doc: Improve documentation for pg_jit_available()
Per complaint from Scott Ribe. Based on wording suggestion from Tom Lane.
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 11, where pg_jit_available() was added
Branch
--
REL_13_STABLE
Doc: Improve documentation for pg_jit_available()
Per complaint from Scott Ribe. Based on wording suggestion from Tom Lane.
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 11, where pg_jit_available() was added
Branch
--
master
Detai
Make EXPLAIN ANALYZE of HashAgg more similar to Hash Join
There were various unnecessary differences between Hash Agg's EXPLAIN
ANALYZE output and Hash Join's. Here we modify the Hash Agg output so
that it's better aligned to Hash Join's.
The following changes have been made:
1. Start batches co
Make EXPLAIN ANALYZE of HashAgg more similar to Hash Join
There were various unnecessary differences between Hash Agg's EXPLAIN
ANALYZE output and Hash Join's. Here we modify the Hash Agg output so
that it's better aligned to Hash Join's.
The following changes have been made:
1. Start batches co
Doc: Remove obsolete CREATE AGGREGATE note.
The planner is in fact willing to use hash aggregation when work_mem is
not set high enough for everything to fit in memory. This has been the
case since commit 1f39bce0, which added disk-based hash aggregation.
There are a few remaining cases in which
Doc: Remove obsolete CREATE AGGREGATE note.
The planner is in fact willing to use hash aggregation when work_mem is
not set high enough for everything to fit in memory. This has been the
case since commit 1f39bce0, which added disk-based hash aggregation.
There are a few remaining cases in which
Correct obsolete UNION hash aggs comment.
Oversight in commit 1f39bce0, which added disk-based hash aggregation.
Backpatch: 13-, where disk-based hash aggregation was introduced.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/b1d79127ed875f04720d2c4677a75f43528bfe
Correct obsolete UNION hash aggs comment.
Oversight in commit 1f39bce0, which added disk-based hash aggregation.
Backpatch: 13-, where disk-based hash aggregation was introduced.
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/b6c15e71f33fe9aa7f38cc7bde26d42
Rename another "hash_mem" local variable.
Missed by my commit 564ce621.
Backpatch: 13-, where disk-based hash aggregation was introduced.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/c49c74d19241b1fc8da6c215ebb40fd6b71c1bff
Modified Files
--
src/bac
Rename another "hash_mem" local variable.
Missed by my commit 564ce621.
Backpatch: 13-, where disk-based hash aggregation was introduced.
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/cdd7bd695bed552936e86b70ff1d234360bc5bea
Modified Files
--
Move syncscan.c to src/backend/access/common.
Since the tableam.c code needs to make use of the syncscan.c routines
itself, and since other block-oriented AMs might also want to use it one
day, it didn't make sense for it to live under src/backend/access/heap.
Reviewed-by: Andres Freund
Discussi
Fix incorrect print format in json.c
Oid is unsigned, so %u needs to be used and not %d. The code path
involved here is not normally reachable, so no backpatch is done.
Author: Justin Pryzby
Discussion: https://postgr.es/m/[email protected]
Branch
--
master
Details
-
14 matches
Mail list logo
