pgsql: Correct heap vacuum boundary state setup ordering

2025-06-02 Thread Melanie Plageman
Correct heap vacuum boundary state setup ordering 052026c9b9 mistakenly reordered setup steps in heap_vacuum_rel(), incorrectly moving RelationGetNumberOfBlocks() before vacuum_get_cutoffs(). OldestXmin must be determined before RelationGetNumberOfBlocks() calculates the number of blocks in the r

pgsql: Disallow "=" in names of reloptions and foreign-data options.

2025-06-02 Thread Tom Lane
Disallow "=" in names of reloptions and foreign-data options. We store values for these options as array elements with the syntax "name=value", hence a name containing "=" confuses matters when it's time to read the array back in. Since validation of the options is often done (long) after this co

pgsql: Disallow "=" in names of reloptions and foreign-data options.

2025-06-02 Thread Tom Lane
Disallow "=" in names of reloptions and foreign-data options. We store values for these options as array elements with the syntax "name=value", hence a name containing "=" confuses matters when it's time to read the array back in. Since validation of the options is often done (long) after this co

pgsql: Disallow "=" in names of reloptions and foreign-data options.

2025-06-02 Thread Tom Lane
Disallow "=" in names of reloptions and foreign-data options. We store values for these options as array elements with the syntax "name=value", hence a name containing "=" confuses matters when it's time to read the array back in. Since validation of the options is often done (long) after this co

pgsql: Disallow "=" in names of reloptions and foreign-data options.

2025-06-02 Thread Tom Lane
Disallow "=" in names of reloptions and foreign-data options. We store values for these options as array elements with the syntax "name=value", hence a name containing "=" confuses matters when it's time to read the array back in. Since validation of the options is often done (long) after this co

pgsql: Disallow "=" in names of reloptions and foreign-data options.

2025-06-02 Thread Tom Lane
Disallow "=" in names of reloptions and foreign-data options. We store values for these options as array elements with the syntax "name=value", hence a name containing "=" confuses matters when it's time to read the array back in. Since validation of the options is often done (long) after this co

pgsql: Rename log_lock_failure GUC to log_lock_failures for consistency

2025-06-02 Thread Fujii Masao
Rename log_lock_failure GUC to log_lock_failures for consistency. This commit renames the GUC log_lock_failure to log_lock_failures to align with the existing similar setting log_lock_waits, which uses the plural form. This improves naming consistency across related GUCs. Suggested-by: Peter Eise

pgsql: Disallow "=" in names of reloptions and foreign-data options.

2025-06-02 Thread Tom Lane
Disallow "=" in names of reloptions and foreign-data options. We store values for these options as array elements with the syntax "name=value", hence a name containing "=" confuses matters when it's time to read the array back in. Since validation of the options is often done (long) after this co

pgsql: Fix incorrect format placeholders

2025-06-02 Thread Peter Eisentraut
Fix incorrect format placeholders Fixes for return type of dclist_count(). Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/fc32be3c941f9d98dd9f549153a5fcea6c3e9b8b Modified Files -- src/backend/storage/aio/aio.c | 10 +- 1 file changed, 5 inserti