Delete Performance
От | P.J. \"Josh\" Rovero |
---|---|
Тема | Delete Performance |
Дата | |
Msg-id | 3BF51BA7.5070304@sonalysts.com обсуждение исходный текст |
Ответы |
Re: Delete Performance
|
Список | pgsql-general |
Tom Lane suggested I look at EXPLAIN output, which showed that both the catalog (fast delete case) and toasted text table (slow delete case) were using sequential scans when deleting any significant number of records.\ But even with sequential scan, the catalog entries are deleted quickly (30K records in just a couple of seconds), vice slow deletes (2 per second) for the toasted text. The catalog entries are about 200 bytes (integers, timestamps, a couple of short fixed length strings), while the toasted text table has one short text field, one timestamp, and one long (2K to 20K bytes) toasted text field. Both will use index scans when a very small number (< 1%) of records would be selected. But relative delete performance stays the same. -- P. J. "Josh" Rovero Sonalysts, Inc. Email: rovero@sonalysts.com www.sonalysts.com 215 Parkway North Work: (860)326-3671 or 442-4355 Waterford CT 06385 ***********************************************************************
В списке pgsql-general по дате отправления: