Re: Protocol 3, Execute, maxrows to return, impact?

Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> "Stephen R. van den Berg" <srb(at)cuci(dot)nl> writes:
>> In practice, most applications that need that, open multiple
>> connections to the same database (I'd think).

> Er? There's nothing particularly unusual about application logic like:

> $sth->execute('huge select');
> while ($sth->fetch('foreign_key')) {
> ... do some processing which is hard to do in server-side language ...
> $sth->execute('insert resulting data');
> }

Moreover, there's often good reasons to do it all within one
transaction, which is impossible if you rely on a separate connection
to issue the inserts on.

regards, tom lane