On Mon, Jan 18, 2021 at 3:25 PM Tom Lane <t...@sss.pgh.pa.us> wrote: > If memory serves, the reason for the lock was that the CHECKPOINT > command used to run the checkpointing code directly in the calling > backend, so we needed it to keep more than one process from doing > that at once. AFAICS, it's no longer possible for more than one > process to try to run that code concurrently, so we shouldn't need > the lock anymore.
Interesting. I think that must have been a *very* long time ago. Perhaps 076a055acf3c55314de267c62b03191586d79cf6 from 2004? -- Robert Haas EDB: http://www.enterprisedb.com