On Fri, Nov 5, 2010 at 22:16, Tom Lane <t...@sss.pgh.pa.us> wrote: > I don't really think that "change the default on Linux" is that > much nicer than "change the default everywhere" when it comes to > what we ought to consider back-patching. In any case, you're getting > ahead of the game: we need to decide on the desired behavior first and > then think about what to patch.
We should be trying to guarantee the stability of maintenance releases. "Stability" includes consistent defaults. The fact that Linux now distinguishes between these two flags has a very surprising effect on PostgreSQL's defaults; an effect that wasn't intended by any developer, is not documented anywhere, and certainly won't be anticipated by users. Do you reject this premise? As newer distros are adopting 2.6.33+ kernels, more and more people will shoot themselves in the foot by this change. I am also worried that it will have a direct effect on PostgreSQL adoption. Regards, Marti -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
