Re: pg_migrator to /contrib in a later 9.0 beta

From: Jesper Krogh <jesper(at)krogh(dot)cc>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_migrator to /contrib in a later 9.0 beta
Date: 2010-05-06 04:53:32
Message-ID: 4BE24B4C.7020108@krogh.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2010-05-06 06:41, Alvaro Herrera wrote:
> Excerpts from Jesper Krogh's message of jue may 06 00:32:09 -0400 2010:
>
>
>> Q: I read you pdf, why isn't statistics copied over? It seems to be the last
>> part missing from doing an upgrade in a few minutes.
>>
> Seems fraught with peril, and a bit pointless. What's so bad about having to
> run ANALYZE afterwards?
>

There is nothing directly "bad" about it.. but:

It's just "an extra step, that might be overseen and is absolutely
required".

I should have written:
Why isn't statistics copied over or why doesnt pg_migrator run analyze by
itself?

The database (of a reasonable size) is useless until statistics is
available.

I guess it is because pg_dump/restore doesn't do it either.

Jesper
--
Jesper

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-05-06 05:35:49 Re: max_standby_delay considered harmful
Previous Message Robert Haas 2010-05-06 04:47:02 Re: max_standby_delay considered harmful