mirror of
https://github.com/postgres/postgres.git
synced 2026-10-23 13:29:09 +03:00
e0fdc3f54b
This reverts commita9c350d9ee. While that intentionally changed our semantics for CREATE SCHEMA subcommands, it's being argued that the functionality gain does not justify potentially-subtle compatibility breakage. The most useful bit of functionality gain came from commit404db8f9e("Execute foreign key constraints in CREATE SCHEMA at the end"), which we're keeping because it's required by SQL spec and doesn't seem to create a compatibility hazard by itself. This is not an exact revert, partly because we're keeping404db8f9e, and partly because I kept the API changes that allowed passing down a ParseState (which allows providing an error cursor for many of the errors thrown in CREATE SCHEMA). Author: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://postgr.es/m/20260904180712.cc.noahmisch@microsoft.com Backpatch-through: 19