pgsql: doc: Move DEFAULT parameter on COPY reference page

doc: Move DEFAULT parameter on COPY reference page The DEFAULT parameter seems most similar to the NULL parameter, so move it next to it, instead of having it at the end of the parameter list because it was the last one added. Branch -- REL_16_STABLE Details --- https://git.postgresql.or

pgsql: doc: Move DEFAULT parameter on COPY reference page

doc: Move DEFAULT parameter on COPY reference page The DEFAULT parameter seems most similar to the NULL parameter, so move it next to it, instead of having it at the end of the parameter list because it was the last one added. Branch -- master Details --- https://git.postgresql.org/pg/co

pgsql: doc: Use proper markup for emphasis

doc: Use proper markup for emphasis Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/3c963d33eae8dcbac0bc2e1dc0b7c1ac931dd83f Modified Files -- doc/src/sgml/config.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

pgsql: doc: Use proper markup for emphasis

doc: Use proper markup for emphasis Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/25da5cd32f73eec9a7ea9b49fbf04d97059ad402 Modified Files -- doc/src/sgml/config.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

pgsql: Fix ALTER EXTENSION SET SCHEMA with objects outside an extension

Fix ALTER EXTENSION SET SCHEMA with objects outside an extension's schema As coded, the code would use as a base comparison the namespace OID from the first object scanned in pg_depend when switching its namespace dependency entry to the new one, and use it as a base of comparison for any follow-u

pgsql: Fix ALTER EXTENSION SET SCHEMA with objects outside an extension

Fix ALTER EXTENSION SET SCHEMA with objects outside an extension's schema As coded, the code would use as a base comparison the namespace OID from the first object scanned in pg_depend when switching its namespace dependency entry to the new one, and use it as a base of comparison for any follow-u

pgsql: Fix ALTER EXTENSION SET SCHEMA with objects outside an extension

Fix ALTER EXTENSION SET SCHEMA with objects outside an extension's schema As coded, the code would use as a base comparison the namespace OID from the first object scanned in pg_depend when switching its namespace dependency entry to the new one, and use it as a base of comparison for any follow-u

pgsql: Fix ALTER EXTENSION SET SCHEMA with objects outside an extension

Fix ALTER EXTENSION SET SCHEMA with objects outside an extension's schema As coded, the code would use as a base comparison the namespace OID from the first object scanned in pg_depend when switching its namespace dependency entry to the new one, and use it as a base of comparison for any follow-u

pgsql: Fix ALTER EXTENSION SET SCHEMA with objects outside an extension

Fix ALTER EXTENSION SET SCHEMA with objects outside an extension's schema As coded, the code would use as a base comparison the namespace OID from the first object scanned in pg_depend when switching its namespace dependency entry to the new one, and use it as a base of comparison for any follow-u

pgsql: Fix ALTER EXTENSION SET SCHEMA with objects outside an extension

Fix ALTER EXTENSION SET SCHEMA with objects outside an extension's schema As coded, the code would use as a base comparison the namespace OID from the first object scanned in pg_depend when switching its namespace dependency entry to the new one, and use it as a base of comparison for any follow-u

pgsql: Fix ALTER EXTENSION SET SCHEMA with objects outside an extension

Fix ALTER EXTENSION SET SCHEMA with objects outside an extension's schema As coded, the code would use as a base comparison the namespace OID from the first object scanned in pg_depend when switching its namespace dependency entry to the new one, and use it as a base of comparison for any follow-u

pgsql: Add more sanity checks with callers of changeDependencyFor()

Add more sanity checks with callers of changeDependencyFor() changeDependencyFor() returns the number of pg_depend entries changed, or 0 if there is a problem. The callers of this routine expect only one dependency to change, but they did not check for the result returned. The following code path