2012/09/24 1:07, Christopher Browne wrote:
We historically have connection pooling as an external thing; with the
high degree to which people keep implementing and reimplementing this, I
think *something* more than we have ought to be built in.
This, with perhaps better implementation, might be
On 23 September 2012 05:50, Satoshi Nagayasu sn...@uptime.jp wrote:
I have just written the first PoC code to enable load balancing
in the libpq library.
This libpq enhancement is intended to allow PostgreSQL users to
take advantage of the replication in easier way.
With using this patch,
Hi all,
I have just written the first PoC code to enable load balancing
in the libpq library.
This libpq enhancement is intended to allow PostgreSQL users to
take advantage of the replication in easier way.
With using this patch, PQconnectdb() function accepts multiple
connection info strings,
On 23-09-2012 07:50, Satoshi Nagayasu wrote:
I have just written the first PoC code to enable load balancing
in the libpq library.
Your POC is totally broken. Just to point out two problems: (i) semicolon (;)
is a valid character for any option in the connection string and (ii) you
didn't
We historically have connection pooling as an external thing; with the high
degree to which people keep implementing and reimplementing this, I think
*something* more than we have ought to be built in.
This, with perhaps better implementation, might be an apropos start.
Parallel with LDAP: it
