| From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Feedback on getting rid of VACUUM FULL |
| Date: | 2009-09-17 14:31:08 |
| Message-ID: | 1253197868.778.181.camel@hvost1700 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2009-09-17 at 10:21 -0400, Tom Lane wrote:
> Hannu Krosing <hannu(at)2ndQuadrant(dot)com> writes:
> > On Wed, 2009-09-16 at 21:19 -0400, Tom Lane wrote:
> >> VACUUM FULL CONCURRENTLY is a contradiction in terms. Wishing it were
> >> possible doesn't make it so.
>
> > It depends on what do you mean by "VACUUM FULL"
>
> Anything that moves tuples is not acceptable as a hidden background
> operation,
I did not mean VACUUM FULL to be run as a hidden background operation.
just as something that does not need everything else to be shut down.
> because it will break applications that depend on CTID.
Do you know of any such applications out in the wild ?
> The utility Heikki is talking about is something that DBAs would
> invoke explicitly, presumably with an understanding of the side effects.
Like VACUUM FULL ?
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-09-17 14:32:42 | Re: Feedback on getting rid of VACUUM FULL |
| Previous Message | Hannu Krosing | 2009-09-17 14:24:53 | Re: Feedback on getting rid of VACUUM FULL |