| From: | Ron St-Pierre <rstpierre(at)syscor(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Table UPDATE is too slow |
| Date: | 2004-09-01 00:18:14 |
| Message-ID: | 41351546.7090600@syscor.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
Thanks for everyone's comments (Thomas, Steinar, Frank, Matt, William).
Right now I'm bench-marking the time it takes for each step
in the end of day update process and then I am going to test a few things:
- dropping most indexes, and check the full processing time and see if
there is any noticeable performance degradation on the web-end
- wrapping the updates in a transaction, and check the timing
- combining the two
- reviewing my shared_buffers and sort_memory settings
Thanks
Ron
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron St-Pierre | 2004-09-01 00:26:37 | Suppress output from psql? |
| Previous Message | Matthew T. O'Connor | 2004-08-31 23:44:33 | Re: Multicolumn Primary Key |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-09-01 05:32:08 | Re: Table UPDATE is too slow |
| Previous Message | Jim C. Nasby | 2004-08-31 22:05:03 | Re: Equivalent praxis to CLUSTERED INDEX? |