Re: Deleting millions of rows
| От | Gregory Stark |
|---|---|
| Тема | Re: Deleting millions of rows |
| Дата | |
| Msg-id | 87iqnqmlaq.fsf@oxford.xeocode.com обсуждение исходный текст |
| Ответ на | Re: Deleting millions of rows (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: Deleting millions of rows
|
| Список | pgsql-performance |
Robert Haas <robertmhaas@gmail.com> writes: > That's good if you're deleting most or all of the parent table, but > what if you're deleting 100,000 values from a 10,000,000 row table? > In that case maybe I'm better off inserting all of the deleted keys > into a side table and doing a merge or hash join between the side > table and the child table... It would be neat if we could feed the queued trigger tests into a plan node like a Materialize and use the planner to determine which type of plan to generate. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support!
В списке pgsql-performance по дате отправления: