pgsql: Move code specific to pg_dependencies to new file

2025-11-11 Thread Michael Paquier
Move code specific to pg_dependencies to new file This new file is named pg_dependencies.c and includes all the code directly related to the data type pg_dependencies, extracted from the extended statistics code. Some patches are under discussion to change its input and output functions, and this

pgsql: Move code specific to pg_ndistinct to new file

2025-11-11 Thread Michael Paquier
Move code specific to pg_ndistinct to new file This new file is named pg_ndistinct.c and includes all the code directly related to the data type pg_ndistinct, extracted from the extended statistics code. Some patches are under discussion to change its input and output functions, and this separati

pgsql: doc: Fix incorrect synopsis for ALTER PUBLICATION ... DROP ...

2025-11-11 Thread Fujii Masao
doc: Fix incorrect synopsis for ALTER PUBLICATION ... DROP ... The synopsis for the ALTER PUBLICATION ... DROP ... command incorrectly implied that a column list and WHERE clause could be specified as part of the publication object. However, these options are not allowed for DROP operations, makin

pgsql: doc: Fix incorrect synopsis for ALTER PUBLICATION ... DROP ...

2025-11-11 Thread Fujii Masao
doc: Fix incorrect synopsis for ALTER PUBLICATION ... DROP ... The synopsis for the ALTER PUBLICATION ... DROP ... command incorrectly implied that a column list and WHERE clause could be specified as part of the publication object. However, these options are not allowed for DROP operations, makin

pgsql: doc: Fix incorrect synopsis for ALTER PUBLICATION ... DROP ...

2025-11-11 Thread Fujii Masao
doc: Fix incorrect synopsis for ALTER PUBLICATION ... DROP ... The synopsis for the ALTER PUBLICATION ... DROP ... command incorrectly implied that a column list and WHERE clause could be specified as part of the publication object. However, these options are not allowed for DROP operations, makin

pgsql: doc: Fix incorrect synopsis for ALTER PUBLICATION ... DROP ...

2025-11-11 Thread Fujii Masao
doc: Fix incorrect synopsis for ALTER PUBLICATION ... DROP ... The synopsis for the ALTER PUBLICATION ... DROP ... command incorrectly implied that a column list and WHERE clause could be specified as part of the publication object. However, these options are not allowed for DROP operations, makin

pgsql: doc: Fix incorrect synopsis for ALTER PUBLICATION ... DROP ...

2025-11-11 Thread Fujii Masao
doc: Fix incorrect synopsis for ALTER PUBLICATION ... DROP ... The synopsis for the ALTER PUBLICATION ... DROP ... command incorrectly implied that a column list and WHERE clause could be specified as part of the publication object. However, these options are not allowed for DROP operations, makin

pgsql: Remove unused assignment in CREATE PUBLICATION grammar.

2025-11-11 Thread Amit Kapila
Remove unused assignment in CREATE PUBLICATION grammar. Commit 96b3784973 extended the grammar for CREATE PUBLICATION to support the ALL SEQUENCES variant. However, it unnecessarily prepared publication objects for this variant, which is not required. This was a copy-paste oversight in that commit

pgsql: Prefer spelling "cacheable" over "cachable".

2025-11-11 Thread Thomas Munro
Prefer spelling "cacheable" over "cachable". Previously we had both in code and comments. Keep the more common and accepted variant. Author: Chao Li Reviewed-by: Peter Smith Reviewed-by: Tom Lane Discussion: https://postgr.es/m/[email protected] Branch -- mas

pgsql: injection_points: Add tests for name limits

2025-11-11 Thread Michael Paquier
injection_points: Add tests for name limits The maximum limits for point name, library name, function name and private area size were not kept track of in the tests. The new function introduced in 16a2f706951e gives a way to trigger them. This is not critical but cheap to cover. While on it, th

pgsql: Report better object limits in error messages for injection poin

2025-11-11 Thread Michael Paquier
Report better object limits in error messages for injection points Previously, error messages for oversized injection point names, libraries, and functions showed buffer sizes (64, 128, 128) instead of the usable character limits (63, 127, 127) as it did not count for the zero-terminated byte, whi

pgsql: Report better object limits in error messages for injection poin

2025-11-11 Thread Michael Paquier
Report better object limits in error messages for injection points Previously, error messages for oversized injection point names, libraries, and functions showed buffer sizes (64, 128, 128) instead of the usable character limits (63, 127, 127) as it did not count for the zero-terminated byte, whi

pgsql: Report better object limits in error messages for injection poin

2025-11-11 Thread Michael Paquier
Report better object limits in error messages for injection points Previously, error messages for oversized injection point names, libraries, and functions showed buffer sizes (64, 128, 128) instead of the usable character limits (63, 127, 127) as it did not count for the zero-terminated byte, whi

pgsql: Add check for large files in meson.build

2025-11-11 Thread Michael Paquier
Add check for large files in meson.build A similar check existed in the MSVC scripts that have been removed in v17 by 1301c80b2167, but nothing of the kind was checked in meson when building with a 4-byte off_t. This commit adds a check to fail the builds when trying to use a relation file size h

pgsql: Add check for large files in meson.build

2025-11-11 Thread Michael Paquier
Add check for large files in meson.build A similar check existed in the MSVC scripts that have been removed in v17 by 1301c80b2167, but nothing of the kind was checked in meson when building with a 4-byte off_t. This commit adds a check to fail the builds when trying to use a relation file size h

pgsql: Add check for large files in meson.build

2025-11-11 Thread Michael Paquier
Add check for large files in meson.build A similar check existed in the MSVC scripts that have been removed in v17 by 1301c80b2167, but nothing of the kind was checked in meson when building with a 4-byte off_t. This commit adds a check to fail the builds when trying to use a relation file size h

pgsql: Add check for large files in meson.build

2025-11-11 Thread Michael Paquier
Add check for large files in meson.build A similar check existed in the MSVC scripts that have been removed in v17 by 1301c80b2167, but nothing of the kind was checked in meson when building with a 4-byte off_t. This commit adds a check to fail the builds when trying to use a relation file size h

pgsql: Tag refs/tags/REL_14_20 was created

2025-11-11 Thread noreply
Tag refs/tags/REL_14_20 was created.

pgsql: Tag refs/tags/REL_13_23 was created

2025-11-11 Thread noreply
Tag refs/tags/REL_13_23 was created.

pgsql: Tag refs/tags/REL_17_7 was created

2025-11-11 Thread noreply
Tag refs/tags/REL_17_7 was created.

pgsql: Tag refs/tags/REL_15_15 was created

2025-11-11 Thread noreply
Tag refs/tags/REL_15_15 was created.

pgsql: Tag refs/tags/REL_16_11 was created

2025-11-11 Thread noreply
Tag refs/tags/REL_16_11 was created.

pgsql: Tag refs/tags/REL_18_1 was created

2025-11-11 Thread noreply
Tag refs/tags/REL_18_1 was created.

pgsql: Add warning to pg_controldata on PG_CONTROL_VERSION mismatch

2025-11-11 Thread Heikki Linnakangas
Add warning to pg_controldata on PG_CONTROL_VERSION mismatch If you run pg_controldata on a cluster that has been initialized with different PG_CONTROL_VERSION than what the pg_controldata program has been compiled with, pg_controldata will still try to interpret the control file, but the result i

pgsql: Add pg_resetwal and pg_controldata support for new control file

2025-11-11 Thread Heikki Linnakangas
Add pg_resetwal and pg_controldata support for new control file field I forgot these in commit 3e0ae46d90. Discussion: https://www.postgresql.org/message-id/[email protected] Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/676cd9ac0743028