aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/advanced.source
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2023-04-04 16:38:06 -0700
committerAndres Freund <andres@anarazel.de>2023-04-04 16:42:52 -0700
commit3f695b31179b94a5eaa284ff588a983ff2dce932 (patch)
treefcbf5a16eb674556784b0be514c2be8d3e19a02c /src/tutorial/advanced.source
parente126d817c7af989c47366b0e344ee83d761f334a (diff)
downloadpostgresql-3f695b31179b94a5eaa284ff588a983ff2dce932.tar.gz
postgresql-3f695b31179b94a5eaa284ff588a983ff2dce932.zip
sequences: Lock buffer before initializing page
fill_seq_fork_with_data(), used to initialize a new sequence relation, only locked the buffer after calling PageInit(), even though PageInit() modifies page contents. This is unlikely to cause real-world issues, as the relation is exclusively locked at that point, and the buffer not yet marked dirty, so other processes should not access the buffer. This issue looks to have been present since the introduction of sequences in e8647c45d66a. Given the low risk, it does not seem worth backpatching the fix. Discussion: https://postgr.es/m/20230404185501.wdkmo3k7bedlx6qk@awork3.anarazel.de
Diffstat (limited to 'src/tutorial/advanced.source')
0 files changed, 0 insertions, 0 deletions