From: | Volkan YAZICI <yazicivo(at)ttmail(dot)com> |
---|---|
To: | sam <sam(dot)mahindrakar(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Performance of update |
Date: | 2008-03-27 11:06:01 |
Message-ID: | 87prtg2zqe.fsf@alamut.mobiliz.com.tr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 26 Mar 2008, sam <sam(dot)mahindrakar(at)gmail(dot)com> writes:
> Iam trying to update a database table with approx 45000 rows. Iam not
> updating all rows at a time. Iam updating 60 rows at a given time for
> example. and this is happening in a FOR LOOP. A function that has the
> update statements is called within the loop.
>
> The updates take too long.....is postgres slow in doing updates on
> large tables or is it because of the function call within the loop???
Are there any ON UPDATE CASACADE and FK consistency checks on the
table. Are related columns used during UPDATE INDEXed appropriately?
It'd be helpful if you can supply your table schema and UPDATE query
string.
Regards.
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2008-03-27 11:11:48 | Re: Performance of update |
Previous Message | Alain Roger | 2008-03-27 10:25:18 | Re: returned value from SQL statement |