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

postgres-lambda-diff

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Andrew Dunstan authored
    Commit ab14a73a raised an error in these cases and later the
    behaviour was copied to jsonb. This is what the XML code, which we
    then adopted, does, as the XSD types don't accept infinite values.
    However, json dates and timestamps are just strings as far as json is
    concerned, so there is no reason not to render these values as
    'infinity'.
    
    The json portion of this is backpatched to 9.4 where the behaviour was
    introduced. The jsonb portion only affects the development branch.
    
    Per gripe on pgsql-general.
    bda76c1c
    History
    Name Last commit Last update