aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2015-08-21 20:32:11 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2015-08-21 20:32:26 -0400
commitfe939d950e362094c14e97f4e91c063374588534 (patch)
tree54d373582e7c3d38d668d49f594941af809dddf7 /src/backend/access/gist/gistproc.c
parent22b9ce79879bdf0aa8ff56ca4973f894ed69813c (diff)
downloadpostgresql-fe939d950e362094c14e97f4e91c063374588534.tar.gz
postgresql-fe939d950e362094c14e97f4e91c063374588534.zip
Avoid O(N^2) behavior when enlarging SPI tuple table in spi_printtup().
For no obvious reason, spi_printtup() was coded to enlarge the tuple pointer table by just 256 slots at a time, rather than doubling the size at each reallocation, as is our usual habit. For very large SPI results, this makes for O(N^2) time spent in repalloc(), which of course soon comes to dominate the runtime. Use the standard doubling approach instead. This is a longstanding performance bug, so back-patch to all active branches. Neil Conway
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions