Re: Optimizer generates bad plans. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Optimizer generates bad plans.
Date
Msg-id 28067.1032551437@sss.pgh.pa.us
Whole thread Raw
In response to Re: Optimizer generates bad plans.  (Kris Jurka <books@ejurka.com>)
List pgsql-hackers
Kris Jurka <books@ejurka.com> writes:
> Looking at the differences in statistics before and after the ANALYZE the
> only differences are in correlation.  This comes from initdb around line
> 1046...

> "$PGPATH"/postgres $PGSQL_OPT template1 >/dev/null <<EOF
> ANALYZE;
> VACUUM FULL FREEZE;
> EOF

> Could this be done better in the one step VACUUM FULL FREEZE ANALYZE or
> ANALYZING after the VACUUM FULL?

Hm.  We can't do it like that, because that would leave the pg_statistic
rows unfrozen.  I suppose we could do

VACUUM FULL;
ANALYZE;
VACUUM FREEZE;
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [PATCHES] to_char(FM9.9) bug fix
Next
From: Alvaro Herrera
Date:
Subject: Re: DROP COLUMN misbehaviour with multiple inheritance