As an example of absurdity of this problem: let's assume there is known distribution with buggy gethostbyname(). Fact, that we know about this, shouldn't stop us developing TCP/IP applications. Especially, if there is also patch for this bug :)

It would be real shame to prevent using generator for SETOF functions because it is most natural match for plpgsql's "return next"

All I was saying was that we need to account for the use of 2.4 :). So as long as we document (as you suggest) we should be good. Sorry if I wasn't clear.

Sincerely,

Joshua D. Drake




--Sven Suursoho



--

           === The PostgreSQL Company: Command Prompt, Inc. ===
     Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
     Providing the most comprehensive  PostgreSQL solutions since 1997
                    http://www.commandprompt.com/



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
      choose an index scan if your joining column's datatypes do not
      match

Reply via email to