Re: Most efficient way for libPQ .. PGresult serialization
От | Craig Ringer |
---|---|
Тема | Re: Most efficient way for libPQ .. PGresult serialization |
Дата | |
Msg-id | CAMsr+YECX0dBH1-f_VRvuRMxNght6H5JR+8FKNGirS5qQx0xWg@mail.gmail.com обсуждение исходный текст |
Ответ на | Most efficient way for libPQ .. PGresult serialization (Joshua Bay <joshuabay93@gmail.com>) |
Ответы |
Re: Most efficient way for libPQ .. PGresult
serialization
|
Список | pgsql-hackers |
On 18 August 2016 at 10:05, Joshua Bay <joshuabay93@gmail.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.
В списке pgsql-hackers по дате отправления: