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

init

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    On reflection this method seems to be exposing an unreasonable amount of
    implementation detail.  It wouldn't matter when talking to a remote server
    of the identical Postgres version, but it seems likely to make things worse
    not better if the remote is a different version with different casting
    infrastructure.  Instead adopt ruleutils.c's policy of regurgitating the
    cast as it was originally specified; including not showing it at all, if
    it was implicit to start with.  (We must do that because for some datatypes
    explicit and implicit casts have different semantics.)
    211e157a
    History
    Name Last commit Last update
    ..