Could we somehow track how many pages we _couldn't_ get into the free
space map, then when the map is empty _and_ we find we have found there
are some pages that we couldn't store during the last vacuum, we throw a
message to the server logs? (Just thinnking out loud.)
-
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Is there any way we can warn users when their fsm parameters are too
> small?
Not until we understand what too small is :-( If anyone's undertaken
any experiments to figure out what an appropriate FSM size setting is,
I'm not aware of it.
The default
Is there any way we can warn users when their fsm parameters are too
small?
---
Tom Lane wrote:
> Ron Mayer <[EMAIL PROTECTED]> writes:
> > logs2=# select pgstattuple('e_ip_full');
> > NOTICE: physical length: 293.84MB liv
Ron Mayer <[EMAIL PROTECTED]> writes:
> logs2=# select pgstattuple('e_ip_full');
> NOTICE: physical length: 293.84MB live tuples: 1697755 (169.26MB, 57.60%)
> dead tuples: 0 (0.00MB, 0.00%) free/reusable space: 110.84MB (37.72%)
> overhead: 4.67%
> pgstattuple
> -
>0
> (1
On Fri, 2 Aug 2002, Tom Lane wrote:
> >> it would be interesting to see what contrib/pgstattuple shows...
> >> if you can run that conveniently.
> > Gladly, if I'm shown where to find it.
> If you built from a source package, the contrib stuff should be in that
> package. If you used RPMs, look
Ron Mayer <[EMAIL PROTECTED]> writes:
>> Also, it would be interesting to see what contrib/pgstattuple shows,
>> if you can run that conveniently.
> Gladly, if I'm shown where to find it.
If you built from a source package, the contrib stuff should be in that
package. If you used RPMs, look for
On Fri, 2 Aug 2002, Tom Lane wrote:
>
> Ron Mayer <[EMAIL PROTECTED]> writes:
> > On a number of my tables, "analyze" seems to be putting the wrong value of
> > "reltuples" in pg_class. "vacuum" seems to be doing the right thing.
>
> Hmm. analyze by itself generates only an approximate estimate
Ron Mayer <[EMAIL PROTECTED]> writes:
> On a number of my tables, "analyze" seems to be putting the wrong value of
> "reltuples" in pg_class. "vacuum" seems to be doing the right thing.
Hmm. analyze by itself generates only an approximate estimate of the
row count (since it only examines a rand