postgres-github.git / summary / log / commit / refs

commit    404db8f9edbb291bcc31542d488fb20f6a965798
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Mon Apr 06 18:52:28 2026 +0000

    Execute foreign key constraints in CREATE SCHEMA at the end.
    
    The previous patch simplified CREATE SCHEMA's behavior to "execute all
    subcommands in the order they are written".  However, that's a bit too
    simple, as the spec clearly requires forward references in foreign key
    constraint clauses to work, see feature F311-01.  (Most other SQL
    implementations seem to read more into the spec than that, but it's
    not clear that there's justification for more in the text, and this is
    the only case that doesn't introduce unresolvable issues.)  We never
    implemented that before, but let's do so now.
    
    To fix it, transform FOREIGN KEY clauses into ALTER TABLE ... ADD
    FOREIGN KEY commands and append them to the end of the CREATE SCHEMA's
    subcommand list.  This works because the foreign key constraints are
    independent and don't affect any other DDL that might be in CREATE
    SCHEMA.  For simplicity, we do this for all FOREIGN KEY clauses even
    if they would have worked where they were.
    
    Author: Jian He <jian.universality@gmail.com>
    Co-authored-by: Tom Lane <tgl@sss.pgh.pa.us>
    Discussion: https://postgr.es/m/1075425.1732993688@sss.pgh.pa.us

[parent: a9c350d9ee66]