Hi, I made the fix and tested it today. It involved some 10-15 lines of code change. I will mail it tomorrow. Feel free to give suggestions on making the fix more maintainable. I have followed Gregory's advice in the fix - Instead of changing the slot_deform_tuple, i have reduced the number of attributes field of the HeapTupleHeader(during insertion), so that the trailing nulls are treated the same as newly added columns. Thanks Gregory. Regarding arrangement of the columns, my take is to leave it to the user on the arrangement of the columns. May be we can put some kind of tuning hint somewhere in our document on the suggestions. I have made the above statement, without thinking about other advantages, if any.
-- Thanks, Gokul. CertoSQL Project, Allied Solution Group. (www.alliedgroups.com)
