| From: | Christopher Browne <cbbrowne(at)acm(dot)org> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Insert slow down on empty database |
| Date: | 2005-06-04 01:20:08 |
| Message-ID: | m3br6msyt3.fsf@knuth.cbbrowne.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
In an attempt to throw the authorities off his trail, "Morgan" <mkita(at)verseon(dot)com> transmitted:
> At first I was using straight insert statments, and although they
> were a bit slower than the prepared statments(after the restablished
> connection) they never ran into this problem with the database being
> initially empty. I only changed to the prepared statements because
> it was suggested in the documentation for advice on bulk data loads
> =).
I remember encountering this with Oracle, and the answer being "do
some loading 'til it slows down, then update statistics and restart."
I don't know that there's an obvious alternative outside of perhaps
some variation on pg_autovacuum...
--
If this was helpful, <http://svcs.affero.net/rm.php?r=cbbrowne> rate me
http://linuxdatabases.info/info/spreadsheets.html
So long and thanks for all the fish.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Junaili Lie | 2005-06-04 01:52:27 | Re: Forcing use of specific index |
| Previous Message | Simon Riggs | 2005-06-03 23:23:57 | Re: Query plan for very large number of joins |