I am running versions 8.1.2 and I installed 8.2B last week. I dumped
the data from a rather large (several million records) from the old into the
new version.
My two observations are as follows... Also, keep in mind these are truly
just observations, I didn't use any benchmarking tools. If
On Mon, 2006-10-23 at 13:36 -0500, [EMAIL PROTECTED] wrote:
2. I have a tsearch2 index which is 756MB in size in 8.1.2 but balloons to
910MB in 8.2! These numbers were taken right after a REINDEX. Normally, I
wouldn't care about physical index size, but this particular index is
sitting on
I am running versions 8.1.2 and I installed 8.2B last week. I dumped
the data from the old version into the new version. The db consists of
several million records. Total disk usage is approximately 114GB.
My two observations are as follows... Also, keep in mind these are truly
just
[EMAIL PROTECTED] writes:
1. The release notes indicate more efficient vacuuming. However, both
vacuums seems to take about the same amount of time, ie. approx: 9 hours.
I think the improvements were only in btree index vacuuming, which it
sounds like isn't your big problem.
2. I have a
2. I have a tsearch2 index which is 756MB in size in 8.1.2 but balloons to
910MB in 8.2!
FILLFACTOR?
Tom,
Of course! I had it in my head that fillfactor had to be explicitely set.
But then, after RTFM, it looks like there are defaults! Thank you!
One more inane question, though.
