On Mon, Aug 2, 2021 at 9:06 AM Dipesh Pandit <dipesh.pan...@gmail.com> wrote: > We can maintain the current timeline ID in archiver specific shared memory. > If we switch to a new timeline then the backend process can update the new > timeline ID in shared memory. Archiver can keep a track of current timeline ID > and if it finds that there is a timeline switch then it can perform a full > directory > scan to make sure that archiving history files takes precedence over WAL > files. > Access to the shared memory area can be protected by adding a WALArchiverLock. > If we take this approach then it doesn't require to use a dedicated signal to > notify > a timeline switch.
Hi, I don't really understand why you are storing something in shared memory specifically for the archiver. Can't we use XLogCtl's ThisTimeLineID instead of storing another copy of the information? Thanks, -- Robert Haas EDB: http://www.enterprisedb.com
