Re: Hot standby and removing VACUUM FULL - Mailing list pgsql-hackers

From Itagaki Takahiro
Subject Re: Hot standby and removing VACUUM FULL
Date
Msg-id 20091124095523.B052.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Hot standby and removing VACUUM FULL  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Hot standby and removing VACUUM FULL
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:

> So I guess what I'm asking is: Does anyone see any show-stoppers in
> removing VACUUM FULL, and does anyone want to step up to the plate and
> promise to do it before release?

I'm working on "New VACUUM FULL" patch, that shrinks tables
using CLUSTER-like rewrites.
https://commitfest.postgresql.org/action/patch_view?id=202

What can I do for the Hot Standby issue?
VACUUM FULL is still reserved for system catalogs in my patch
because we cannot modify relfilenodes for the catalog tables.
Do you have solutions for it?

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center




pgsql-hackers by date:

Previous
From: Itagaki Takahiro
Date:
Subject: Re: TRIGGER with WHEN clause
Next
From: Itagaki Takahiro
Date:
Subject: Re: EXPLAIN BUFFERS