Re: cutting out the middleperl - Mailing list pgsql-general

From Aidan Van Dyk
Subject Re: cutting out the middleperl
Date
Msg-id euba1q$nnk$1@sea.gmane.org
Whole thread Raw
In response to cutting out the middleperl  ("Kev" <kevinjamesfield@gmail.com>)
Responses Re: cutting out the middleperl  (Steve Atkins <steve@blighty.com>)
Re: cutting out the middleperl  ("Kev" <kevinjamesfield@gmail.com>)
Re: cutting out the middleperl  ("Merlin Moncure" <mmoncure@gmail.com>)
List pgsql-general
Kev wrote:

> Hi everyone,
>
> I'm still in the design phase of a project.  I was just wondering if
> anyone has any thoughts or experience on the idea of cutting the P out
> of the LAMP (or in my case, WAMP for now) stack.  What I mean is
> having
> everything encapsulated into sql (or plpgsql or plperl where needed)
> functions stored in the pgsql server, and have Apache communicate with
> pgsql via a tiny C program that pretty much just checks whether the
> incoming function is on the allowed list and has the proper data
> types,
> then passes it straight in.  Any errors are logged as potential
> security
> breaches.

Sounds something like mod_libpq:
   http://asmith.id.au/mod_libpq.html



pgsql-general by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: [pgsql-advocacy] Is there a shortage of postgresql skilled ops people
Next
From: "Dmitry Koterov"
Date:
Subject: Strange behaviour under heavy load