Re: Protocol 3, Execute, maxrows to return, impact? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Protocol 3, Execute, maxrows to return, impact?
Date
Msg-id 10953.1215710679@sss.pgh.pa.us
Whole thread Raw
In response to Re: Protocol 3, Execute, maxrows to return, impact?  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Gregory Stark <stark@enterprisedb.com> writes:
> "Stephen R. van den Berg" <srb@cuci.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


pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Protocol 3, Execute, maxrows to return, impact?
Next
From: Fabrízio de Royes Mello
Date:
Subject: digest