Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while
Date
Msg-id 603c8f071002111042y40971cfbod4628a2028925d67@mail.gmail.com
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while
List pgsql-hackers
On Thu, Feb 11, 2010 at 1:33 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> Avoiding a scan before running pg_upgrade is just a performance
> optimisation.

But using pg_upgrade AT ALL is also a performance optimization; in
fact AFAICS it's the only reason to use pg_upgrade.  So if you take
that away there's no reason to use it at all.

...Robert


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] Provide rowcount for utility SELECTs