| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while |
| Date: | 2010-02-11 18:42:13 |
| Message-ID: | 603c8f071002111042y40971cfbod4628a2028925d67@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Thu, Feb 11, 2010 at 1:33 PM, Simon Riggs <simon(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-02-11 19:03:08 | Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while |
| Previous Message | Simon Riggs | 2010-02-11 18:33:16 | Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-02-11 18:52:12 | Re: [PATCH] Provide rowcount for utility SELECTs |
| Previous Message | Simon Riggs | 2010-02-11 18:33:16 | Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while |