Hi Anthonin, > [...] > > The usual approach is to have pre-allocated memory. This must actually be > written (zeroed usually) or it might be lazily allocated only on page fault. > And it can't be copy on write memory allocated once in postmaster startup > then inherited by fork. > > That imposes an overhead for every single postgres backend. So maybe there's > a better solution.
It looks like the patch rotted a bit, see cfbot. Could you please submit an updated version? Best regards, Aleksander Alekseev (wearing co-CFM hat)
