pgsql: Remove unnecessary (char *) casts [mem]

Remove unnecessary (char *) casts [mem] Remove (char *) casts around memory functions such as memcmp(), memcpy(), or memset() where the cast is useless. Since these functions don't take char * arguments anyway, these casts are at best complicated casts to (void *), about which see commit 7f798aca

pgsql: Remove unnecessary (char *) casts [string]

Remove unnecessary (char *) casts [string] Remove (char *) casts around string functions where the arguments or result already have the right type and the cast is useless (or worse, potentially casts away a qualifier, but this doesn't appear to be the case here). Reviewed-by: Dagfinn Ilmari Manns

pgsql: Doc: Fix punctuation errors

Doc: Fix punctuation errors Author: 斉藤登 Reviewed-by: David G. Johnston Discussion: https://postgr.es/m/caam3qnl6i-bsu5rb2+kihljmcoxiqeipmbvej7f1cguzzmo...@mail.gmail.com Backpatch-through: 13 Branch -- REL_17_STABLE Details --- https://git.postgresql.org/pg/commitdiff/fa761d9c71375ec4

pgsql: Doc: Fix punctuation errors

Doc: Fix punctuation errors Author: 斉藤登 Reviewed-by: David G. Johnston Discussion: https://postgr.es/m/caam3qnl6i-bsu5rb2+kihljmcoxiqeipmbvej7f1cguzzmo...@mail.gmail.com Backpatch-through: 13 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/0bc34ad69204dded9cd06d0

pgsql: Doc: Fix punctuation errors

Doc: Fix punctuation errors Author: 斉藤登 Reviewed-by: David G. Johnston Discussion: https://postgr.es/m/caam3qnl6i-bsu5rb2+kihljmcoxiqeipmbvej7f1cguzzmo...@mail.gmail.com Backpatch-through: 13 Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/d29bf192e5498418

pgsql: Doc: Fix punctuation errors

Doc: Fix punctuation errors Author: 斉藤登 Reviewed-by: David G. Johnston Discussion: https://postgr.es/m/caam3qnl6i-bsu5rb2+kihljmcoxiqeipmbvej7f1cguzzmo...@mail.gmail.com Backpatch-through: 13 Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/412047f19fcb9785

pgsql: Doc: Fix punctuation errors

Doc: Fix punctuation errors Author: 斉藤登 Reviewed-by: David G. Johnston Discussion: https://postgr.es/m/caam3qnl6i-bsu5rb2+kihljmcoxiqeipmbvej7f1cguzzmo...@mail.gmail.com Backpatch-through: 13 Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/80b23bf5b858d54c

pgsql: Doc: Fix punctuation errors

Doc: Fix punctuation errors Author: 斉藤登 Reviewed-by: David G. Johnston Discussion: https://postgr.es/m/caam3qnl6i-bsu5rb2+kihljmcoxiqeipmbvej7f1cguzzmo...@mail.gmail.com Backpatch-through: 13 Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/9efd78ef6b091904

pgsql: Tag refs/tags/REL_15_11 was created

Tag refs/tags/REL_15_11 was created.

pgsql: Tag refs/tags/REL_14_16 was created

Tag refs/tags/REL_14_16 was created.

pgsql: Tag refs/tags/REL_16_7 was created

Tag refs/tags/REL_16_7 was created.

pgsql: Tag refs/tags/REL_17_3 was created

Tag refs/tags/REL_17_3 was created.

pgsql: Tag refs/tags/REL_13_19 was created

Tag refs/tags/REL_13_19 was created.

pgsql: Add is_analyze parameter to vacuum_delay_point().

Add is_analyze parameter to vacuum_delay_point(). This function is used in both vacuum and analyze code paths, and a follow-up commit will require distinguishing between the two. This commit forces callers to specify whether they are in a vacuum or analyze path, but it does not use that informati

pgsql: Add cost-based vacuum delay time to progress views.

Add cost-based vacuum delay time to progress views. This commit adds the amount of time spent sleeping due to cost-based delay to the pg_stat_progress_vacuum and pg_stat_progress_analyze system views. A new configuration parameter named track_cost_delay_timing, which is off by default, controls w

pgsql: Limit pgbench COPY FREEZE to ordinary relations

Limit pgbench COPY FREEZE to ordinary relations pgbench client-side data generation uses COPY FREEZE to load data for most tables. COPY FREEZE isn't supported for partitioned tables and since pgbench only supports partitioning pgbench_accounts, pgbench used a hard-coded check to skip COPY FREEZE a

pgsql: Injection points for hash aggregation.

Injection points for hash aggregation. Requires adding a guard against shift-by-32. Previously, that was impossible because the number of partitions was always greater than 1, but a new injection point can force the number of partitions to 1. Discussion: https://postgr.es/m/ff4e59305e5d689e03cd2

pgsql: Eagerly scan all-visible pages to amortize aggressive vacuum

Eagerly scan all-visible pages to amortize aggressive vacuum Aggressive vacuums must scan every unfrozen tuple in order to advance the relfrozenxid/relminmxid. Because data is often vacuumed before it is old enough to require freezing, relations may build up a large backlog of pages that are set a

pgsql: config: Split "Worker Processes" out of "Asynchronous Behavior"

config: Split "Worker Processes" out of "Asynchronous Behavior" Having all the worker related GUCs in the same section as IO controlling GUCs doesn't really make sense. Create a separate section for them. Reviewed-by: Tom Lane Discussion: https://postgr.es/m/x3tlw2jk5gm3r3mv47hwrshffyw7halpczkf

pgsql: config: Rename "Asynchronous Behavior" to "I/O"

config: Rename "Asynchronous Behavior" to "I/O" "I/O" seems more descriptive than "Asynchronous Behavior", given that some of the GUCs in the section don't relate to anything asynchronous. Most other abbreviations in the config sections are un-abbreviated, but "Input/Output" seems less likely to

pgsql: Refactor pl_funcs.c to provide a usage-independent tree walker.

Refactor pl_funcs.c to provide a usage-independent tree walker. We haven't done this up to now because there was only one use-case, namely plpgsql_free_function_memory's search for expressions to clean up. However an upcoming patch has another need for walking plpgsql functions' statement trees,

pgsql: Detect whether plpgsql assignment targets are "local" variables.

Detect whether plpgsql assignment targets are "local" variables. Mark whether the target of a potentially optimizable assignment is "local", in the sense of being declared inside any exception block that could trap an error thrown from the assignment. (This implies that we needn't preserve the var

pgsql: Allow extension functions to participate in in-place updates.

Allow extension functions to participate in in-place updates. Commit 1dc5ebc90 allowed PL/pgSQL to perform in-place updates of expanded-object variables that are being updated with assignments like "x := f(x, ...)". However this was allowed only for a hard-wired list of functions f(), since we ne

pgsql: Preliminary refactoring of plpgsql expression construction.

Preliminary refactoring of plpgsql expression construction. This short and boring patch simply moves the responsibility for initializing PLpgSQL_expr.target_param into plpgsql parsing, rather than doing it at first execution of the expr as before. This doesn't save anything in terms of runtime, si

pgsql: Implement new optimization rule for updates of expanded variable

Implement new optimization rule for updates of expanded variables. If a read/write expanded variable is declared locally to the assignment statement that is updating it, and it is referenced exactly once in the assignment RHS, then we can optimize the operation as a direct update of the expanded v

pgsql: Replace AssertMacro() with Assert() when not in macro

Replace AssertMacro() with Assert() when not in macro This was forgotten to be changed in commit 9c727360bcc. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/6998db59c2959c4f280a9088054e6dbf7178efe0 Modified Files -- src/include/storage/bufmgr.h | 2 +-