Skip site navigation (1) Skip section navigation (2)

Re: HTTP Frontend? (and a brief thought on materialized views)

From: Daniel Farina <daniel(at)heroku(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Dobes Vandermeer <dobesv(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: HTTP Frontend? (and a brief thought on materialized views)
Date: 2012-03-30 17:44:20
Message-ID: CAAZKuFapGZC49bsM8qFZtSQSAga6t8D38x1tSG_83feZ3+00Sw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, Mar 30, 2012 at 10:21 AM, Daniel Farina <daniel(at)heroku(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-03-30 17:49:24
Subject: Re: pg_dump incredibly slow dumping a single schema from a large db
Previous:From: Mike RoestDate: 2012-03-30 17:33:38
Subject: Re: pg_dump incredibly slow dumping a single schema from a large db

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group