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

tupdesc.c

  • Tom Lane's avatar
    8e144080
    Make equalTupleDescs() compare attlen/attbyval/attalign rather than · 8e144080
    Tom Lane authored
    assuming comparison of atttypid is sufficient.  In a dropped column
    atttypid will be 0, and we'd better check the physical-storage data
    to make sure the tupdescs are physically compatible.
    I do not believe there is a real risk before 8.0, since before that
    we only used this routine to compare successive states of the tupdesc
    for a particular relation.  But 8.0's typcache.c might be comparing
    arbitrary tupdescs so we'd better play it safer.
    8e144080
    History
    Make equalTupleDescs() compare attlen/attbyval/attalign rather than
    Tom Lane authored
    assuming comparison of atttypid is sufficient.  In a dropped column
    atttypid will be 0, and we'd better check the physical-storage data
    to make sure the tupdescs are physically compatible.
    I do not believe there is a real risk before 8.0, since before that
    we only used this routine to compare successive states of the tupdesc
    for a particular relation.  But 8.0's typcache.c might be comparing
    arbitrary tupdescs so we'd better play it safer.