On 12 August 2013 18:37, Peter Eisentraut wrote:
> On 8/8/13 3:44 PM, Josh Berkus wrote:
> > Other than that, no. I was thinking of creating a general tool as a
> > custom background worker, which would take stored procedure calls and
> > pass them through to PostgreSQL, returning results as JSO
On 8/8/13 3:44 PM, Josh Berkus wrote:
> Other than that, no. I was thinking of creating a general tool as a
> custom background worker, which would take stored procedure calls and
> pass them through to PostgreSQL, returning results as JSON. Mainly
> because I need it for a project. However, thi
Josh Berkus writes:
> Agreed. Too bad you can't do this as an extension, it would allow you
> to rev releases a lot faster than once a year.
> Actually, maybe you should look at "what is the minimum patch required
> to enable a webserver extension", with the idea that most of the
> webserver cod
> For my patch, I plan to use pre-forked bgworkers which have already
> connected to the backend, so that populating the relcache and other process
> startup costs don't impact on the HTTP response time. (This still means
> queries are being planned and function code is being compiled for each
>
On 9 Aug 2013 17:03, "Greg Stark" wrote:
> I looked at the wiki and thought it had a lot of good ideas but also a
lot of good questions. do you have any idea how to tackle the session
problem?
> [...]
> A decent HTTP RPC layer will need to have some way of creating a session
and issuing multiple r
On Fri, Aug 9, 2013 at 9:21 AM, Andrew Tipton wrote:
> I recently threw together a quick-and-dirty prototype of this idea. It
> was an external tool which used the libmicrohttpd library to accept
> incoming requests, convert them to a SQL query (which called a stored
> procedure), and return the
On Fri, Aug 9, 2013 at 3:44 AM, Josh Berkus wrote:
> Well, there's HTSQL: http://htsql.org/
>
> Other than that, no. I was thinking of creating a general tool as a
> custom background worker, which would take stored procedure calls and
> pass them through to PostgreSQL, returning results as JSON
On Fri, Aug 9, 2013 at 2:44 AM, Szymon Guz wrote:
>
> Do we have any attempts of implementation the HTTP server described at
> http://wiki.postgresql.org/wiki/HTTP_API?
>
> It seems like there are design ideas only. Are there any ideas about
> implementation like using some existing http servers
On 08/08/2013 11:44 AM, Szymon Guz wrote:
> Do we have any attempts of implementation the HTTP server described at
> http://wiki.postgresql.org/wiki/HTTP_API?
>
> It seems like there are design ideas only. Are there any ideas about
> implementation like using some existing http servers or writing
Do we have any attempts of implementation the HTTP server described at
http://wiki.postgresql.org/wiki/HTTP_API?
It seems like there are design ideas only. Are there any ideas about
implementation like using some existing http servers or writing everything
from scratch?
regards
Szymon
10 matches
Mail list logo
