| From: | Sean Davis <sdavis2(at)mail(dot)nih(dot)gov> |
|---|---|
| To: | Andy <frum(at)ar-sd(dot)net>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Massive delete performance |
| Date: | 2005-10-11 11:54:39 |
| Message-ID: | BF71203F.10300%sdavis2@mail.nih.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 10/11/05 3:47 AM, "Andy" <frum(at)ar-sd(dot)net> wrote:
> Hi to all,
>
> I have the following problem: I have a client to which we send every night a
> "dump" with a the database in which there are only their data's. It is a
> stupid solution but I choose this solution because I couldn't find any better.
> The target machine is a windows 2003.
>
> So, I have a replication only with the tables that I need to send, then I make
> a copy of this replication, and from this copy I delete all the data's that
> are not needed.
>
> How can I increase this DELETE procedure because it is really slow??? There
> are of corse a lot of data's to be deleted.
Do you have foreign key relationships that must be followed for cascade
delete? If so, make sure that you have indices on them. Are you running
any type of vacuum after the whole process? What kind?
Sean
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy | 2005-10-11 12:05:52 | Re: Massive delete performance |
| Previous Message | Simon Riggs | 2005-10-11 08:02:57 | Re: Compression of text columns |