If we are going to back-patch more aggressively, we _have_ to be sureI know that I am probably being semantic here but I in know way want to be more aggressive with back patching. My
that those back-patched releases have the same quality as all our other
releases.
thoughts for 98% of things in on bugfixes within the existing tree only. Although I am sure for some things we can
use (at least as a guide) code being written in 7.4. My whole purpose in bringing the idea up is to increase the adoption rate.
My thought isn't to be more agressive per say, but more responsible in our releases. Like I said, I may be, being semantic.
Sincerely,
Joshua Drake
I know people already know this, but it is worth mentioning specifically --- my point is that more agressive backpatching has risks.
-- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - [EMAIL PROTECTED] - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org
---------------------------(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
