Re: Speed dblink using alternate libpq tuple storage

Kyotaro Horiguchi <horiguchi.kyotaro@oss.ntt.co.jp>

From: Kyotaro HORIGUCHI <horiguchi.kyotaro@oss.ntt.co.jp>
To: markokr@gmail.com
Cc: pgsql-hackers@postgresql.org, greg@2ndquadrant.com, shigeru.hanada@gmail.com, mmoncure@gmail.com
Date: 2012-02-21T09:55:46Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix COPY FROM for null marker strings that correspond to invalid encoding.

  2. Improve labeling of pg_test_fsync open_sync test output.

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