Re: [PERFORM] DELETE vs TRUNCATE explanation - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PERFORM] DELETE vs TRUNCATE explanation
Date
Msg-id 13011.1342457859@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PERFORM] DELETE vs TRUNCATE explanation  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [PERFORM] DELETE vs TRUNCATE explanation  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> In my view, the elephant in the room here is that it's dramatically
> inefficient for every backend to send an fsync request on every block
> write.

Yeah.  This was better before the decision was taken to separate
bgwriter from checkpointer; before that, only local communication was
involved for the bulk of write operations (or at least so we hope).
I remain less than convinced that that split was really a great idea.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PERFORM] DELETE vs TRUNCATE explanation
Next
From: Robert Haas
Date:
Subject: Re: Getting rid of pre-assignment of index names in CREATE TABLE LIKE