aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuild.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2023-03-22 09:26:23 -0700
committerAndres Freund <andres@anarazel.de>2023-03-22 09:26:23 -0700
commit560bb56c6eba5da7917e67783d46f0d5ca30e89a (patch)
tree1636c19449a402440e31ffb111a116395a5c44fd /src/backend/access/gist/gistbuild.c
parenta70e6e430628fe5ee802f47f4b043d33a0d41dda (diff)
downloadpostgresql-560bb56c6eba5da7917e67783d46f0d5ca30e89a.tar.gz
postgresql-560bb56c6eba5da7917e67783d46f0d5ca30e89a.zip
Fix memory leak and inefficiency in CREATE DATABASE ... STRATEGY WAL_LOG
RelationCopyStorageUsingBuffer() did not free the strategies used to access the source / target relation. They memory was released at the end of the transaction, but when using a template database with a lot of relations, the temporary leak can become big prohibitively big. RelationCopyStorageUsingBuffer() acquired the buffer for the target relation with RBM_NORMAL, therefore requiring a read of a block guaranteed to be zero. Use RBM_ZERO_AND_LOCK instead. Reviewed-by: Robert Haas <robertmhaas@gmail.com> Discussion: https://postgr.es/m/20230321070113.o2vqqxogjykwgfrr@awork3.anarazel.de Backpatch: 15-, where STRATEGY WAL_LOG was introduced
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions