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
    Tom Lane authored
    Since range types can be created by non-superusers, we need to consider
    their permissions.  Ideally we'd check this when the type is used, not
    when it's created, but that seems like much more trouble than it's worth.
    The existing restriction that the support functions be immutable already
    prevents most cases where an unauthorized call to a function might be
    thought a security issue, and the fact that the user has no access to
    the results of the system's calls to subtype_diff closes off the other
    plausible reason for concern.  So this check is basically pro-forma,
    but let's make it anyway.
    a912a278
    History
    Name Last commit Last update