Re: Async IO HTTP server frontend for PostgreSQL

From: Dmitriy Igrishin <dmitigr(at)gmail(dot)com>
To: John DeSoi <desoi(at)pgedit(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Async IO HTTP server frontend for PostgreSQL
Date: 2014-09-10 17:02:51
Message-ID: CAAfz9KNxL=Cd5xP8E1j-8ZEnVMZUKS9q7exB1nVh1nT8UToEYg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello, John

2014-09-10 17:25 GMT+04:00 John DeSoi <desoi(at)pgedit(dot)com>:

>
> On Sep 9, 2014, at 7:31 PM, David Boreham <david_list(at)boreham(dot)org> wrote:
>
> > Hi Dmitriy, are you able to say a little about what's driving your quest
> for async http-to-pg ?
> > I'm curious as to the motivations, and whether they match up with some
> of my own reasons for wanting to use low-thread-count solutions.
>
> For some discussion and preliminary design, see also
>
> https://wiki.postgresql.org/wiki/HTTP_API
>
> John DeSoi, Ph.D.
>
While this is not related to the %subj%, I've glanced and the link above.
And I found this complex. (As many many many "nice featured" things
on the market today.) Could you tell me please, for example, why the
URLs like
/databases/:database_name/schemas/:schema_name/tables/:table_name
OR
/databases/:database_name/schemas/:schema_name/table/:table_name/indexes/:index_name
Whats wrong with SQL way to get such info from sys. catalogs or
the information schema?
I guess, I know the answer -- "its just pretty nice and clear". But
I think it's just a waste of time (of users which should learn all of
these fancies, and developers which should implement them).

--
// Dmitriy.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Steve Atkins 2014-09-10 17:08:00 Re: Async IO HTTP server frontend for PostgreSQL
Previous Message Tom Lane 2014-09-10 16:15:29 Re: CREATE SYNONYM in PostgreSQL