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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Protocol 3, Execute, maxrows to return, impact?
Дата
Msg-id 10953.1215710679@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Protocol 3, Execute, maxrows to return, impact?  (Gregory Stark <stark@enterprisedb.com>)
Список 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 по дате отправления:

Предыдущее
От: Gregory Stark
Дата:
Сообщение: Re: Protocol 3, Execute, maxrows to return, impact?
Следующее
От: Fabrízio de Royes Mello
Дата:
Сообщение: digest