Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

include

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    Instead put in a test to drop a NULL default at the last moment before
    storing the catalog entry.  This changes the behavior in a couple of ways:
    * Specifying DEFAULT NULL when creating an inheritance child table will
      successfully suppress inheritance of any default expression from the
      parent's column, where formerly it failed to do so.
    * Specifying DEFAULT NULL for a column of a domain type will correctly
      override any default belonging to the domain; likewise for a sub-domain.
    The latter change happens because by the time the clause is checked,
    it won't be a simple null Const but a CoerceToDomain expression.
    
    Personally I think this should be back-patched, but there doesn't seem to
    be consensus for that on pgsql-hackers, so refraining.
    b17b7fae
    History
    Name Last commit Last update
    ..