VJK wrote:
> Since Pg does not use the concept of rollback segments, it is unclear
> why deletion produces so much disk IO (4GB).
With PostgreSQL's write-ahead log, MVCC and related commit log, and
transactional DDL features, there's actually even more overhead that can
be involved than a simple rollback segment design when you delete things:
http://www.postgresql.org/docs/current/static/wal.htmlhttp://www.postgresql.org/docs/current/static/mvcc-intro.htmlhttp://wiki.postgresql.org/wiki/Hint_Bitshttp://wiki.postgresql.org/wiki/Transactional_DDL_in_PostgreSQL:_A_Competitive_Analysis
One fun thing to try here is to increase shared_buffers and
checkpoint_segments, then see if the total number of writes go down.
The defaults for both are really low, which makes buffer page writes
that might otherwise get combined as local memory changes instead get
pushed constantly to disk.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com www.2ndQuadrant.us
