From: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
---|---|
To: | Dobes Vandermeer <dobesv(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Http Frontend implemented using pgsql? |
Date: | 2012-03-31 13:36:07 |
Message-ID: | CAC_2qU8qCd42eHmN8YCtYFPh09=vCaOrkwt+PDrb6d4_sJX4Ng@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Mar 31, 2012 at 6:27 AM, Dobes Vandermeer <dobesv(at)gmail(dot)com> wrote:
> I had a thought that it might be interesting to have a simple C fronted that
> converts HTTP to and from some pgsql friendly structure and delegates all
> the core logic to a stored procedure in the database.
>
> This might make it easier to hack on the API without worrying about memory
> management and buffer overflow vulnerabilities.
>
> Is this a brain wave or a brain fart?
Something along the lines of a stripped down mod_libpq?
http://asmith.id.au/mod_libpq.html
If we had something along the lines of JSON <-> Row/setof in core, I
could see this being a very nice "RPC" mechanism for PostgreSQL.
Plain HTTP still give's you the session/transaction control problem of
stateless clients, but maybe coupled with PgPool you could cobble
something together...
a.
--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dobes Vandermeer | 2012-03-31 13:37:14 | Re: HTTP Frontend? (and a brief thought on materialized views) |
Previous Message | Greg Stark | 2012-03-31 12:58:51 | Re: measuring lwlock-related latency spikes |