Re: Speed dblink using alternate libpq tuple storage

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)oss(dot)ntt(dot)co(dot)jp>
To: markokr(at)gmail(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org, greg(at)2ndquadrant(dot)com, shigeru(dot)hanada(at)gmail(dot)com, mmoncure(at)gmail(dot)com
Subject: Re: Speed dblink using alternate libpq tuple storage
Date: 2012-02-21 09:55:46
Message-ID: 20120221.185546.00505398.horiguchi.kyotaro@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sorry, I should fix a wrong word selection..

> Let me confirm the effects of this function. Is the below
> description right?
>
> - PQskipResult(conn, false) makes just following PQgetResult() to
> skip current bunch of rows and the consequent PQgetResult()'s
> gathers rows as usual.

- PQskipResult(conn, false) makes just following PQgetResult() to
skip current bunch of rows and the succeeding PQgetResult()'s
gathers rows as usual. ~~~~~~~~~~

> - PQskipResult(conn, true) makes all consequent PQgetResult()'s
> to skip all the rows.

- PQskipResult(conn, true) makes all succeeding PQgetResult()'s
to skip all the rows. ~~~~~~~~~~

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2012-02-21 09:56:50 Re: Speed dblink using alternate libpq tuple storage
Previous Message Kyotaro HORIGUCHI 2012-02-21 09:42:34 Re: Speed dblink using alternate libpq tuple storage