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

cluster.c

  • Tom Lane's avatar
    475cb157
    Squash some more CLUSTER bugs. Never has worked on multiple-column · 475cb157
    Tom Lane authored
    indexes, apparently, nor on functional indexes with more than one input
    column (force of natts = 1 was in the wrong branch of IF statement).
    Coredumped if source relation contained any uncommitted tuples, due to
    failure to test for success return from heap_fetch.  Fetched tuple
    was passed directly to heap_insert, which clobbers the TID and commit
    status in the tuple header it's given, which meant that the source
    relation's tuples all got trashed as the copy proceeded.  Abort partway
    through, and you're left with a lot of missing tuples.
    I wonder what else is lurking here ...
    475cb157
    History
    Squash some more CLUSTER bugs. Never has worked on multiple-column
    Tom Lane authored
    indexes, apparently, nor on functional indexes with more than one input
    column (force of natts = 1 was in the wrong branch of IF statement).
    Coredumped if source relation contained any uncommitted tuples, due to
    failure to test for success return from heap_fetch.  Fetched tuple
    was passed directly to heap_insert, which clobbers the TID and commit
    status in the tuple header it's given, which meant that the source
    relation's tuples all got trashed as the copy proceeded.  Abort partway
    through, and you're left with a lot of missing tuples.
    I wonder what else is lurking here ...