>>> Tom Lane <[EMAIL PROTECTED]> wrote: > I think a large fraction of the writes you're measuring are coming from > the file create/unlink operations. It would certainly be important to > identify where the bulk of the cost *really* is before we start > expending effort on a solution. Any ideas on a good way to gather that information? Given the temp_buffers space, would it make sense to defer the creation of the actual file until there is actually a need to spill data to the disk? -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
