Re: Most efficient way for libPQ .. PGresult serialization

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: craig(at)2ndquadrant(dot)com
Cc: joshuabay93(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Most efficient way for libPQ .. PGresult serialization
Date: 2016-08-18 05:33:17
Message-ID: 20160818.143317.1337807404635546038.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 18 August 2016 at 10:05, Joshua Bay <joshuabay93(at)gmail(dot)com> wrote:
>
>> Hi,
>>
>> I was trying to implement a middleware that lies between client and
>> postgres.
>>
>> So, this middleware is supposed to run query with libpq, do its job on
>> them, and then serialize the result of query, and send it to the client !
>> (client deserializes to PGresult)
>>
>> I could simply iterate over rows and columns but than that would be slow.
>> I also found that query results consist of 3 parts (PGresult, tuples, data
>> blocks).
>>
>> Could I please get some pointers ? :)
>>
>>
> Take a look at the code for PgBouncer and PgPool-II. Both implement
> PostgreSQL protocol proxies you could use as starting points.

This one is based on Pgpool-II.

https://github.com/treasure-data/prestogres

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-08-18 05:37:50 Re: patch proposal
Previous Message Venkata B Nagothi 2016-08-18 05:15:45 Re: patch proposal