Hi John, Thanks. Agree, the reindexes will take forever to finish. Do you think increase temp_buffers will help too?
Regards, Haiming [cid:logo_new_96ac6d31-abb9-4f10-a3b7-74542f8c4a5f1111111111111111111111111111111.png] Haiming Zhang | Engineer | Redflex Group T +61 3 9674 1868 | F +61 3 9699 3566 | E haiming.zh...@redflex.com.au 31 Market Street, (PO Box 720), South Melbourne VIC 3205, Australia If you are not an authorised recipient of this e-mail, please contact me at Redflex immediately by return phone call or by email. In this case, you should not read, print, retransmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. This e-mail and any attachments are confidential and may contain privileged information and/or copyright material of Redflex or third parties. You should only retransmit, distribute or commercialise the material if you are authorised to do so. This notice should not be removed. From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce Sent: Monday, 16 May 2016 3:28 PM To: pgsql-general@postgresql.org Subject: Re: [GENERAL] Fast way to delete big table? On 5/15/2016 10:23 PM, Gavin Flower wrote: 4. recreate indexes for tableA note on a large table, this step can take a LONG time. its greatly facilitated by setting maintenance_work_mem = 1G beforehand. -- john r pierce, recycling bits in santa cruz
