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_fdw

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    Autovacuum occurring while the test runs could allow some of the inserts to
    go into recycled space, thus changing the output ordering of later queries.
    While we could complicate those queries to force sorting of their output
    rows, it doesn't seem like that would make the test better in any
    meaningful way, and conceivably it could hide unexpected diffs.  Instead,
    tweak the affected queries so that the inserted rows aren't updated by the
    following UPDATE.  Per buildfarm.
    e0b451e4
    History
    Name Last commit Last update
    ..