From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Paul A Vixie <vixie(at)mfnx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: day 2 results |
Date: | 2000-12-20 19:02:42 |
Message-ID: | 3A410252.60AB9B52@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> VACUUM ANALYZE after the INSERTs made no performance difference at all,
> which is good since no other modern database requires anything to be done
> to improve performance after a large number of INSERTs. (i can understand
> why COPY would need it, but not INSERT.)
afaik every modern database requires something like this to update
optimizer stats, since on-the-fly stats accumulation can be expensive
and inaccurate. But most of my recent experience has been with
PostgreSQL and perhaps some other DBs have added some hacks to get
around this. Of course, some databases advertised as modern don't do
much optimization, so don't need the stats.
The biggest effect seen is when growing from an empty database, when the
stats would be changing the most. Once populated, the stats update
usually has little effect, but shouldn't be ignored forever.
Glad to see the tests are going well...
- Thomas
btw, I'll guess that "no other" and "every" could both be
overstatements, but it sure makes a better sentence, eh? ;)
From | Date | Subject | |
---|---|---|---|
Next Message | Marc SCHAEFER | 2000-12-20 19:04:50 | Re: Re: [ADMIN] Help me for "DBI->connect failed: Sorry, too many clients already." |
Previous Message | Larry Rosenman | 2000-12-20 18:44:35 | Re: performance modality in 7.1 for large text attributes? |