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
    Robert Haas authored
    Previously, the foreign join pushdown infrastructure left the question
    of security entirely up to individual FDWs, but it would be easy for
    a foreign data wrapper to inadvertently open up subtle security holes
    that way.  So, make it the core code's job to determine which user
    mapping OID is relevant, and don't attempt join pushdown unless it's
    the same for all relevant relations.
    
    Per a suggestion from Tom Lane.  Shigeru Hanada and Ashutosh Bapat,
    reviewed by Etsuro Fujita and KaiGai Kohei, with some further
    changes by me.
    fbe5a3fb
    History
    Name Last commit Last update