On Sunday 20 February 2005 00:30, Tom Lane wrote:
> Mark Kirkwood <[EMAIL PROTECTED]> writes:
> > To be fair to Mark, there does seem to be an increasing number of
> > reports of this issue. In spite of the in-the-works fix for 8.1, it
> > would be a pity to see customers losing data from xid wrap-around.
>
> The question is whether we are willing to back-patch a fairly large
> amount of not-very-well-tested code into 8.0. See
> http://archives.postgresql.org/pgsql-patches/2005-02/msg00123.php
> http://archives.postgresql.org/pgsql-committers/2005-02/msg00127.php
> http://archives.postgresql.org/pgsql-committers/2005-02/msg00131.php
>
> I personally don't think it's worth the risk. The code works well
> enough to commit to development tip, but it's fundamentally alpha
> quality code.
>
I would lean away from putting it in 8.0, however aren't we planning an 8.0.x
release that will have a beta and/or rc testing for arc related changes? If
so I might be open to putting it in that release (though the bits requiring
initdb are a killer).
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
