Andrew - Supernews <[EMAIL PROTECTED]> writes: > I believe this could usefully (and transparently to clients) be changed > so that Bind on the unnamed statement does _not_ store the plan back in > the unnamed statement's context, but instead produces a plan which is > only used _for that specific portal_.
That seems OK to me, since we document the unnamed statement/portal as being optimized for one-shot execution. Unfortunately it's probably less than a trivial change, because the planner never assumes that Params are constants; that would have to be changed somehow. regards, tom lane ---------------------------(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