| From: | ptjm(at)interlog(dot)com (Patrick TJ McPhee) |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Performance Question |
| Date: | 2006-06-16 04:37:06 |
| Message-ID: | 4feqriF1itp3nU1@uni-berlin.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
In article <200606141557(dot)37321(dot)terry(at)esc1(dot)com>,
Terry Lee Tucker <terry(at)esc1(dot)com> wrote:
% elements of 50 thousand records on 8 structurally identical databases. We
% threw together the script and decided to just delete the record and re-insert
% it with the data that was brought into sync. Now the question: Is it just as
% fast to do it this way, or is there some hidden advantage to performing an
% update?
If you have foreign key relationships to the table being updated, then
deleting from that table will often be slower than updating.
--
Patrick TJ McPhee
North York Canada
ptjm(at)interlog(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | snacktime | 2006-06-16 05:08:16 | minimizing downtime when upgrading |
| Previous Message | Chander Ganesan | 2006-06-16 04:21:14 | Re: Omitting tablespace creation from pg_dumpall... |