aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/jsonpath_exec.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2021-12-13 09:58:36 -0500
committerRobert Haas <rhaas@postgresql.org>2021-12-13 09:58:36 -0500
commitfa0e03c15a9f67671f0a6e0ec66d5e2ac7119c8a (patch)
tree3807601544f0a6f9237759cc5331e94e15136fbe /src/backend/utils/adt/jsonpath_exec.c
parent64da07c41a8c0a680460cdafc79093736332b6cf (diff)
downloadpostgresql-fa0e03c15a9f67671f0a6e0ec66d5e2ac7119c8a.tar.gz
postgresql-fa0e03c15a9f67671f0a6e0ec66d5e2ac7119c8a.zip
Remove InitXLOGAccess().
It's not great that RecoveryInProgress() calls InitXLOGAccess(), because a status inquiry function typically shouldn't have the side effect of performing initializations. We could fix that by calling InitXLOGAccess() from some other place, but instead, let's remove it altogether. One thing InitXLogAccess() did is initialize wal_segment_size, but it doesn't need to do that. In the postmaster, PostmasterMain() calls LocalProcessControlFile(), and all child processes will inherit that value -- except in EXEC_BACKEND bulds, but then each backend runs SubPostmasterMain() which also calls LocalProcessControlFile(). The other thing InitXLOGAccess() did is update RedoRecPtr and doPageWrites, but that's not critical, because all code that uses them will just retry if it turns out that they've changed. The only difference is that most code will now see an initial value that is definitely invalid instead of one that might have just been way out of date, but that will only happen once per backend lifetime, so it shouldn't be a big deal. Patch by me, reviewed by Nathan Bossart, Michael Paquier, Andres Freund, Heikki Linnakangas, and Álvaro Herrera. Discussion: http://postgr.es/m/CA+TgmoY7b65qRjzHN_tWUk8B4sJqk1vj1d31uepVzmgPnZKeLg@mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/jsonpath_exec.c')
0 files changed, 0 insertions, 0 deletions