I think that's great news! If the code is written in a conforming way, I don't see why a new release would be a cause for headaches. And if new compiler releases *are* a cause for headaches, it doesn't give me great confidence in the codebase.
Uhmmm that isn't always true. The switch from 2.x to 3.x was fairly painful. Standards can change and do often.
Sincerely,
Joshua D. Drake
-- Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240 PostgreSQL Replication, Consulting, Custom Programming, 24x7 support Managed Services, Shared and Dedication Hosting Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
---------------------------(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
