| 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 19:46:07 |
| Message-ID: | 25169.1342467967@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:
> Yes, it seems to have done just that. The comment for
> ForwardFsyncRequest is a few bricks short of a load too:
> ...
> Line 2 seems to have been mechanically changed from "background
> writer" to "checkpointer", but of course it should still say
> "background writer" in this case.
Yeah, found that one already (it's probably my fault).
Will see about fixing the stats in a separate patch. I just wanted to
know if the issue had been dealt with in some non-obvious fashion.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Wilson | 2012-07-16 19:56:25 | Re: BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2) |
| Previous Message | Robert Haas | 2012-07-16 19:26:38 | Re: [PERFORM] DELETE vs TRUNCATE explanation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2012-07-16 20:01:21 | Re: very very slow inserts into very large table |
| Previous Message | Robert Haas | 2012-07-16 19:26:38 | Re: [PERFORM] DELETE vs TRUNCATE explanation |