| From: | "Igal (at) Lucee(dot)org" <igal(at)lucee(dot)org> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ian Barwick <ian(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: RETURNING primary_key() |
| Date: | 2016-03-09 16:41:11 |
| Message-ID: | 56E05227.2060005@lucee.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/8/2016 5:12 PM, Craig Ringer wrote:
> One of the worst problems (IMO) is in the driver architecture its
> self. It attempts to prevent blocking by guestimating the server's
> send buffer state and its recv buffer state, trying to stop them
> filling and causing the server to block on writes. It should just
> avoid blocking on its own send buffer, which it can control with
> confidence. Or use some of Java's rather good concurrency/threading
> features to simultaneously consume data from the receive buffer and
> write to the send buffer when needed, like pgjdbc-ng does.
Are there good reasons to use pgjdbc over pgjdbc-ng then?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2016-03-09 16:45:47 | Re: multivariate statistics v14 |
| Previous Message | Tom Lane | 2016-03-09 16:28:14 | Re: More stable query plans via more predictable column statistics |