Florian G. Pflug wrote:
> Since we didn't really reach an agreement on how xid_age should behave,
> I've reverted it back to the original version. So with this patch,
> xid_age will just force assignment of a xid.
Is this really a good idea? I'm repeating myself, but a query like
select age(xmin) from bigtable
could accelerate Xid wraparound. If the server is running close to the
limit it could cause a shutdown to prevent the actual wraparound.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
