diff options
author | Andres Freund <andres@anarazel.de> | 2023-04-05 08:19:39 -0700 |
---|---|---|
committer | Andres Freund <andres@anarazel.de> | 2023-04-05 08:19:39 -0700 |
commit | 3d6a98457d8e21d85bed86cfd3e1d1df1b260721 (patch) | |
tree | e305eaf6f711f1b334a5e35224c022e90430dc05 /src/backend/access/gist/gistbuild.c | |
parent | 86a3fc7ec8a03bca7120894bababa7c734628b4c (diff) | |
download | postgresql-3d6a98457d8e21d85bed86cfd3e1d1df1b260721.tar.gz postgresql-3d6a98457d8e21d85bed86cfd3e1d1df1b260721.zip |
Don't initialize page in {vm,fsm}_extend(), not needed
The read path needs to be able to initialize pages anyway, as relation
extensions are not durable. By avoiding initializing pages, we can, in a
future patch, extend the relation by multiple blocks at once.
Using smgrextend() for {vm,fsm}_extend() is not a good idea in general, as at
least one page of the VM/FSM will be read immediately after, always causing a
cache miss, requiring us to read content we just wrote.
Discussion: https://postgr.es/m/20230301223515.pucbj7nb54n4i4nv@awork3.anarazel.de
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions