On Fri, Mar 30, 2012 at 10:21 AM, Daniel Farina <daniel@heroku.com> wrote:
> Any enhancement here that can't be used with libpq via, say, drop-in
> .so seems unworkable to me, and that's why any solution that is
> basically proxying to the database is basically a non-starter outside
> the very earliest prototyping stages. The tuple scanning and protocol
> semantics can and even should remain the same, especially at first.
I should add: proxying could work well if libpq had all the right
hooks. The server could remain ignorant. Regardless, upstream changes
result.
--
fdr