From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Daniel Farina <daniel(at)heroku(dot)com>, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, Harold A(dot) Giménez <harold(dot)gimenez(at)gmail(dot)com> |
Subject: | Re: [PERFORM] DELETE vs TRUNCATE explanation |
Date: | 2012-07-16 16:57:39 |
Message-ID: | 13011.1342457859@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Robert Haas <robertmhaas(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-07-16 16:58:49 | Re: Getting rid of pre-assignment of index names in CREATE TABLE LIKE |
Previous Message | Robert Haas | 2012-07-16 16:53:02 | Re: [PERFORM] DELETE vs TRUNCATE explanation |
From | Date | Subject | |
---|---|---|---|
Next Message | Samuel Gendler | 2012-07-16 17:35:32 | Re: very very slow inserts into very large table |
Previous Message | Robert Haas | 2012-07-16 16:53:02 | Re: [PERFORM] DELETE vs TRUNCATE explanation |