diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-05-13 22:48:09 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-05-13 22:48:26 -0400 |
commit | 7fd89f4d7a51af77175a876613cffb490b9e5df1 (patch) | |
tree | 48c2a1d47b328e04d04a8c98200225cf4999c864 /src/backend/access/gist/gistvalidate.c | |
parent | d82a5058fdb5905abc9867da302000c39aa30f01 (diff) | |
download | postgresql-7fd89f4d7a51af77175a876613cffb490b9e5df1.tar.gz postgresql-7fd89f4d7a51af77175a876613cffb490b9e5df1.zip |
Fix async.c to not register any SLRU stats counts in the postmaster.
Previously, AsyncShmemInit forcibly initialized the first page of the
async SLRU, to save dealing with that case in asyncQueueAddEntries.
But this is a poor tradeoff, since many installations do not ever use
NOTIFY; for them, expending those cycles in AsyncShmemInit is a
complete waste. Besides, this only saves a couple of instructions
in asyncQueueAddEntries, which hardly seems likely to be measurable.
The real reason to change this now, though, is that now that we track
SLRU access stats, the existing code is causing the postmaster to
accumulate some access counts, which then get inherited into child
processes by fork(), messing up the statistics. Delaying the
initialization into the first child that does a NOTIFY fixes that.
Hence, we can revert f3d23d83e, which was an incorrect attempt at
fixing that issue. Also, add an Assert to pgstat.c that should
catch any future errors of the same sort.
Discussion: https://postgr.es/m/8367.1589391884@sss.pgh.pa.us
Diffstat (limited to 'src/backend/access/gist/gistvalidate.c')
0 files changed, 0 insertions, 0 deletions