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
    Eventually we might be able to allow that, but it's not clear how many
    places need to be fixed to prevent infinite recursion when there's a direct
    or indirect inclusion of a rowtype in itself.  One such place is
    CheckAttributeType(), which will recurse to stack overflow in cases such as
    those exhibited in bug #5950 from Alex Perepelica.  If we were sure it was
    the only such place, we could easily modify the code added by this patch to
    stop the recursion without a complaint ... but it probably isn't the only
    such place.  Hence, throw error until such time as someone is excited
    enough about this type of usage to put work into making it safe.
    
    Back-patch as far as 8.3.  8.2 doesn't have the recursive call in
    CheckAttributeType in the first place, so I see no need to add code there
    in the absence of clear evidence of a problem elsewhere.
    eb51af71
    History
    Name Last commit Last update