pgsql: docs: fix text by adding/removing parentheses

2025-11-07 Thread Bruce Momjian
docs: fix text by adding/removing parentheses Reported-by: Daisuke Higuchi Author: Daisuke Higuchi, Erik Wienhold Reviewed-by: Erik Wienhold Discussion: https://postgr.es/m/CAEVT6c9FRQcFCzQ8AO=qoeqna-w6rhtkfouhzy6n2xd5ynb...@mail.gmail.com Backpatch-through: master Branch -- master Det

pgsql: Remove blank line in C code.

2025-11-07 Thread Bruce Momjian
Remove blank line in C code. Was added in commit 5e89985928795f243dc287210c2aa016dfd00bfe. Reported-by: Ashutosh Bapat Author: Ashutosh Bapat Discussion: https://postgr.es/m/CAExHW5tba_biyuMrd_iPVzq-+XvsMdPcEnjQ+d+__V=cjyj...@mail.gmail.com Backpatch-through: master Branch -- master Det

pgsql: Fix generic read and write barriers for Clang.

2025-11-07 Thread Thomas Munro
Fix generic read and write barriers for Clang. generic-gcc.h maps our read and write barriers to C11 acquire and release fences using compiler builtins, for platforms where we don't have our own hand-rolled assembler. This is apparently enough for GCC, but the C11 memory model is only defined in

pgsql: Fix generic read and write barriers for Clang.

2025-11-07 Thread Thomas Munro
Fix generic read and write barriers for Clang. generic-gcc.h maps our read and write barriers to C11 acquire and release fences using compiler builtins, for platforms where we don't have our own hand-rolled assembler. This is apparently enough for GCC, but the C11 memory model is only defined in

pgsql: Fix generic read and write barriers for Clang.

2025-11-07 Thread Thomas Munro
Fix generic read and write barriers for Clang. generic-gcc.h maps our read and write barriers to C11 acquire and release fences using compiler builtins, for platforms where we don't have our own hand-rolled assembler. This is apparently enough for GCC, but the C11 memory model is only defined in

pgsql: Fix generic read and write barriers for Clang.

2025-11-07 Thread Thomas Munro
Fix generic read and write barriers for Clang. generic-gcc.h maps our read and write barriers to C11 acquire and release fences using compiler builtins, for platforms where we don't have our own hand-rolled assembler. This is apparently enough for GCC, but the C11 memory model is only defined in

pgsql: Fix generic read and write barriers for Clang.

2025-11-07 Thread Thomas Munro
Fix generic read and write barriers for Clang. generic-gcc.h maps our read and write barriers to C11 acquire and release fences using compiler builtins, for platforms where we don't have our own hand-rolled assembler. This is apparently enough for GCC, but the C11 memory model is only defined in

pgsql: Fix generic read and write barriers for Clang.

2025-11-07 Thread Thomas Munro
Fix generic read and write barriers for Clang. generic-gcc.h maps our read and write barriers to C11 acquire and release fences using compiler builtins, for platforms where we don't have our own hand-rolled assembler. This is apparently enough for GCC, but the C11 memory model is only defined in

pgsql: Fix generic read and write barriers for Clang.

2025-11-07 Thread Thomas Munro
Fix generic read and write barriers for Clang. generic-gcc.h maps our read and write barriers to C11 acquire and release fences using compiler builtins, for platforms where we don't have our own hand-rolled assembler. This is apparently enough for GCC, but the C11 memory model is only defined in

pgsql: Fix checking for recovery state in WaitForLSN()

2025-11-07 Thread Alexander Korotkov
Fix checking for recovery state in WaitForLSN() We only need to do it for WAIT_LSN_TYPE_REPLAY. WAIT_LSN_TYPE_FLUSH can work for both primary and follower. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/7742f99a02ed1679eb6baeb35491ea3cf8a3a36e Modified Files

pgsql: First-draft release notes for 18.1.

2025-11-07 Thread Tom Lane
First-draft release notes for 18.1. As usual, the release notes for other branches will be made by cutting these down, but put them up for community review first. Also as usual for a .1 release, there are some entries here that are not really relevant for v18 because they already appeared in 18.0

pgsql: doc: Fix incorrect wording for --file in pg_dump

2025-11-07 Thread Daniel Gustafsson
doc: Fix incorrect wording for --file in pg_dump The documentation stated that the directory specified by --file must not exist, but pg_dump does allow for empty directories to be specified and used. Author: Daniel Gustafsson Reviewed-by: Bruce Momjian Discussion: https://postgr.es/m/534aa60d-c

pgsql: pgbench: Add --continue-on-error option.

2025-11-07 Thread Fujii Masao
pgbench: Add --continue-on-error option. This commit adds the --continue-on-error option, allowing pgbench clients to continue running even when SQL statements fail for reasons other than serialization or deadlock errors. Without this option (by default), the clients aborts in such cases, which wa

pgsql: Fix "inconsistent DLL linkage" warning on Windows MSVC

2025-11-07 Thread Peter Eisentraut
Fix "inconsistent DLL linkage" warning on Windows MSVC This warning was disabled in meson.build (warning 4273). If you enable it, it looks like this: ../src/backend/utils/misc/ps_status.c(27): warning C4273: '__p__environ': inconsistent dll linkage C:\Program Files (x86)\Windows Kits\10\includ

pgsql: Add seq_sync_error_count to subscription statistics.

2025-11-07 Thread Amit Kapila
Add seq_sync_error_count to subscription statistics. This commit adds a new column, seq_sync_error_count, to the pg_stat_subscription_stats view. This counter tracks the number of errors encountered by the sequence synchronization worker during operation. Since a single worker handles the synchro