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

heaptuple.c

Blame
    • Tom Lane's avatar
      3212cf94
      Distinguish between MaxHeapAttributeNumber and MaxTupleAttributeNumber, · 3212cf94
      Tom Lane authored
      where the latter is made slightly larger to allow for in-memory tuples
      containing resjunk attributes.  Responds to today's complaint that one
      cannot UPDATE a table containing the allegedly-legal maximum number of
      columns.
      
      Also, apply Manfred Koizar's recent patch to avoid extra alignment padding
      when there is a null bitmap.  This saves bytes in some cases while not
      creating any backward-compatibility problem AFAICS.
      3212cf94
      History
      Distinguish between MaxHeapAttributeNumber and MaxTupleAttributeNumber,
      Tom Lane authored
      where the latter is made slightly larger to allow for in-memory tuples
      containing resjunk attributes.  Responds to today's complaint that one
      cannot UPDATE a table containing the allegedly-legal maximum number of
      columns.
      
      Also, apply Manfred Koizar's recent patch to avoid extra alignment padding
      when there is a null bitmap.  This saves bytes in some cases while not
      creating any backward-compatibility problem AFAICS.