Robert Haas <robertmhaas@xxxxxxxxx> writes: > On Thu, Oct 28, 2010 at 5:26 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: >> It's true that we don't know whether write() causes an immediate or >> delayed disk write, but we generally don't care that much. What we do >> care about is being able to ensure that a WAL write happens before the >> data write, and with mmap we don't have control over that. > Well, we COULD keep the data in shared buffers, and then copy it into > an mmap()'d region rather than calling write(), but I'm not sure > there's any advantage to it. Managing address space mappings is a > pain in the butt. In principle that ought to be right about the same speed as using write() to copy the data from shared buffers to kernel disk buffers, anyway. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
