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

access

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    for inserting tuples in increasing TID order.  It's not clear whether this
    fully explains Ivan Sergio Borgonovo's complaint, but simple testing
    confirms that a scan that doesn't start at block 0 can slow GIN build by
    a factor of three or four.
    
    Backpatch to 8.3.  Sync scan didn't exist before that.
    10e3acb8
    History
    Name Last commit Last update
    ..
    common
    gin
    gist
    hash
    heap
    index
    nbtree
    transam
    Makefile