pgsql: Rationalize handling of VacuumParams

Rationalize handling of VacuumParams This commit refactors the vacuum routines that rely on VacuumParams, adding const markers where necessary to force a new policy in the code. This structure should not use a pointer as it may be used across multiple relations, and its contents should never be up

pgsql: Branch REL_18_STABLE was created

Branch REL_18_STABLE was created. View: https://git.postgresql.org/pg/shortlog/refs/heads/REL_18_STABLE

pgsql: Align log_line_prefix in CI and TAP tests with pg_regress.c

Align log_line_prefix in CI and TAP tests with pg_regress.c log_line_prefix is changed to include "%b", the backend type in the TAP test configuration. %v and %x are removed from the CI configuration, with the format around %b changed. The lack of backend type in postgresql.conf set by Cluster.p

pgsql: Adapt REL_18_STABLE to its new status as a stable branch

Adapt REL_18_STABLE to its new status as a stable branch Per the checklist in RELEASE_CHANGES for the creation of a new stable branch, this commit does the following things: - Arm gen_node_support.pl's nodetag ABI stability, based on the contents of nodetags.h. - Update URLs of top-level README an

pgsql: Stamp HEAD as 19devel.

Stamp HEAD as 19devel. Let the hacking begin ... Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/2652835d3efa003439ecc23d5fc3cf089c5952a6 Modified Files -- configure| 18 +- configure.ac |2 +- doc/src/sgml/fileli

pgsql: Do pre-release housekeeping on catalog data.

Do pre-release housekeeping on catalog data. Run renumber_oids.pl to move high-numbered OIDs down, as per pre-beta tasks specified by RELEASE_CHANGES. For reference, the command was ./renumber_oids.pl --first-mapped-oid 8000 --target-oid 6300 This should have been done prior to beta1, but it wa

pgsql: Run pgperltidy

Run pgperltidy This is required before the creation of a new branch. pgindent is clean, as well as is reformat-dat-files. perltidy version is v20230309, as documented in pgindent's README. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/0ebd24255581837f9a5b189ef15

pgsql: Fix some new issues with planning of PlaceHolderVars.

Fix some new issues with planning of PlaceHolderVars. In the wake of commit a16ef313f, we need to deal with more cases involving PlaceHolderVars in NestLoopParams than we did before. For one thing, a16ef313f was incorrect to suppose that we could rely on the required-outer relids of the lefthand

pgsql: Obtain required table lock during cross-table constraint updates

Obtain required table lock during cross-table constraint updates. Sometimes a table's constraint may depend on a column of another table, so that we have to update the constraint when changing the referenced column's type. We need to have lock on the constraint's table to do that. ATPostAlterTyp

pgsql: Obtain required table lock during cross-table constraint updates

Obtain required table lock during cross-table constraint updates. Sometimes a table's constraint may depend on a column of another table, so that we have to update the constraint when changing the referenced column's type. We need to have lock on the constraint's table to do that. ATPostAlterTyp

pgsql: Obtain required table lock during cross-table constraint updates

Obtain required table lock during cross-table constraint updates. Sometimes a table's constraint may depend on a column of another table, so that we have to update the constraint when changing the referenced column's type. We need to have lock on the constraint's table to do that. ATPostAlterTyp

pgsql: Obtain required table lock during cross-table constraint updates

Obtain required table lock during cross-table constraint updates. Sometimes a table's constraint may depend on a column of another table, so that we have to update the constraint when changing the referenced column's type. We need to have lock on the constraint's table to do that. ATPostAlterTyp

pgsql: Obtain required table lock during cross-table constraint updates

Obtain required table lock during cross-table constraint updates. Sometimes a table's constraint may depend on a column of another table, so that we have to update the constraint when changing the referenced column's type. We need to have lock on the constraint's table to do that. ATPostAlterTyp

pgsql: Obtain required table lock during cross-table constraint updates

Obtain required table lock during cross-table constraint updates. Sometimes a table's constraint may depend on a column of another table, so that we have to update the constraint when changing the referenced column's type. We need to have lock on the constraint's table to do that. ATPostAlterTyp

pgsql: pg_recvlogical: Rename --two-phase and --failover options.

pg_recvlogical: Rename --two-phase and --failover options. This commit renames the pg_recvlogical options --two-phase and --failover to --enable-two-phase and --enable-failover, respectively. The new names distinguish these enabling options from action options like --start and --create-slot, while