Re: Hot Standby, release candidate? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Hot Standby, release candidate?
Date
Msg-id 11858.1260816533@sss.pgh.pa.us
Whole thread Raw
In response to Re: Hot Standby, release candidate?  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Hot Standby, release candidate?
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
>  * Disallow clustering system relations.  This will definitely NOT work
>  * for shared relations (we have no way to update pg_class rows in other
>  * databases), nor for nailed-in-cache relations (the relfilenode values
>  * for those are hardwired, see relcache.c).  It might work for other
>  * system relations, but I ain't gonna risk it.

> I would presume we would not want to relax the restriction on CLUSTER
> working on these tables, even if new VACUUM FULL does.

Why not?  If we solve the problem of allowing these relations to change
relfilenodes, then CLUSTER would work just fine on them.  Whether it's
particularly useful is not ours to decide I think.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Python 3.1 support
Next
From: Peter Eisentraut
Date:
Subject: Re: Python 3.1 support