Thread: proposal GSoC 2015 task: Allow access to the database via HTTP

proposal GSoC 2015 task: Allow access to the database via HTTP

From
Вадим Горбачев
Date:
<div dir="ltr"><font face="monospace, monospace">Hi Team.<br /><br />I would like to solve a problem of "Allow access
tothe database via HTTP". <br /><br />But before drawing up the demand in GSOC I wanted to consult here. Therefore I
willbe grateful to comments from attendees here!<br /><br />1. I think, will better use access to DB through the
stand-aloneprogram which not necessarily has to be on the same server. At least because it will give certain freedom in
clustersystems.<br /><br />2. Whether it is obligatory to use a programming language C for this purpose? After all as
thestand-alone program ( frontend ) it has to be not necessarily written in the same programming language as the server
(backend ). I would prefer to use the python language for writing as I consider that this language is more clear to
systemadministrators + to bring much more simply editings in a code.<br /><br />3. What you will advise what to pass a
selectionstage in GSOC 2015 from postgresql?)<br /><br />PS: my English is poor. I ask you to forgive me for it.<br
/><br/>Best Regards,<br />Vadim Gorbachov</font><br /></div> 

Re: proposal GSoC 2015 task: Allow access to the database via HTTP

From
Вадим Горбачев
Date:
as prompted to me, already there are solutions of this task: pgrest and OpenResty

Then it isn't clear why this task is in TODO the sheet https://wiki.postgresql.org/wiki/Todo...
Prompt what exactly is understood as "Allow access to the database via HTTP"?
From what party to approach this task?
Whether it still also is actual?

Best Regards,
Vadim Gorbachov

2015-03-23 1:28 GMT+03:00 Вадим Горбачев <bmsdave@gmail.com>:
Hi Team.

I would like to solve a problem of "Allow access to the database via HTTP".

But before drawing up the demand in GSOC I wanted to consult here. Therefore I will be grateful to comments from attendees here!

1. I think, will better use access to DB through the stand-alone program which not necessarily has to be on the same server. At least because it will give certain freedom in cluster systems.

2. Whether it is obligatory to use a programming language C for this purpose? After all as the stand-alone program ( frontend ) it has to be not necessarily written in the same programming language as the server ( backend ). I would prefer to use the python language for writing as I consider that this language is more clear to system administrators + to bring much more simply editings in a code.

3. What you will advise what to pass a selection stage in GSOC 2015 from postgresql?)

PS: my English is poor. I ask you to forgive me for it.

Best Regards,
Vadim Gorbachov


Re: proposal GSoC 2015 task: Allow access to the database via HTTP

From
Pavel Stehule
Date:
Hi

2015-03-22 23:28 GMT+01:00 Вадим Горбачев <bmsdave@gmail.com>:
Hi Team.

I would like to solve a problem of "Allow access to the database via HTTP".

But before drawing up the demand in GSOC I wanted to consult here. Therefore I will be grateful to comments from attendees here!

1. I think, will better use access to DB through the stand-alone program which not necessarily has to be on the same server. At least because it will give certain freedom in cluster systems.

2. Whether it is obligatory to use a programming language C for this purpose? After all as the stand-alone program ( frontend ) it has to be not necessarily written in the same programming language as the server ( backend ). I would prefer to use the python language for writing as I consider that this language is more clear to system administrators + to bring much more simply editings in a code.

What is a benefit of this implementation for Postgres community?

Proposed implementation is few lines in Python - and it is not big benefit for us. More, similar project exists.

It can be interesting as well integrated project to Postgres - implemented in C as background worker (if it possible)

Regards

Pavel
 

3. What you will advise what to pass a selection stage in GSOC 2015 from postgresql?)

PS: my English is poor. I ask you to forgive me for it.

Best Regards,
Vadim Gorbachov


Fwd: proposal GSoC 2015 task: Allow access to the database via HTTP

From
Вадим Горбачев
Date:
>> What is a benefit of this implementation for Postgres community? 
It will be possible to clean this task from https://wiki.postgresql.org/wiki/Todo

>> It can be interesting as well integrated project to Postgres - implemented in C as background worker (if it possible)
I.e. as I understand http_api has to work in separate process at the server of the DBMS.

And why not to start the free-standing application?
In this case there will be great opportunities for scaling:
1. through one http_api appendix it will be possible to be connected to several DB
2. to use pgpool
3. to share burden between servers and so forth.
4. to carry out other functions of a frontend.

And what pluses writing of background worker will give?

If background worker is necessary, I am ready to realize it and it will be interesting to me.
But whether it will be more necessary for postgresql, than the free-standing application?


2015-03-23 19:24 GMT+03:00 Pavel Stehule <pavel.stehule@gmail.com>:
Hi

2015-03-22 23:28 GMT+01:00 Вадим Горбачев <bmsdave@gmail.com>:
Hi Team.

I would like to solve a problem of "Allow access to the database via HTTP".

But before drawing up the demand in GSOC I wanted to consult here. Therefore I will be grateful to comments from attendees here!

1. I think, will better use access to DB through the stand-alone program which not necessarily has to be on the same server. At least because it will give certain freedom in cluster systems.

2. Whether it is obligatory to use a programming language C for this purpose? After all as the stand-alone program ( frontend ) it has to be not necessarily written in the same programming language as the server ( backend ). I would prefer to use the python language for writing as I consider that this language is more clear to system administrators + to bring much more simply editings in a code.

What is a benefit of this implementation for Postgres community?

Proposed implementation is few lines in Python - and it is not big benefit for us. More, similar project exists.

It can be interesting as well integrated project to Postgres - implemented in C as background worker (if it possible)

Regards

Pavel
 

3. What you will advise what to pass a selection stage in GSOC 2015 from postgresql?)

PS: my English is poor. I ask you to forgive me for it.

Best Regards,
Vadim Gorbachov




Re: proposal GSoC 2015 task: Allow access to the database via HTTP

From
Вадим Горбачев
Date:

2015-03-23 20:26 GMT+03:00 Pavel Stehule <pavel.stehule@gmail.com>:


2015-03-23 18:10 GMT+01:00 Вадим Горбачев <bmsdave@gmail.com>:
>> What is a benefit of this implementation for Postgres community? 
It will be possible to clean this task from https://wiki.postgresql.org/wiki/Todo

>> It can be interesting as well integrated project to Postgres - implemented in C as background worker (if it possible)
I.e. as I understand http_api has to work in separate process at the server of the DBMS.

And why not to start the free-standing application?
In this case there will be great opportunities for scaling:
1. through one http_api appendix it will be possible to be connected to several DB
2. to use pgpool
3. to share burden between servers and so forth.
4. to carry out other functions of a frontend.

And what pluses writing of background worker will give?

integration to Postgres - simply (usual) deployment. Fast access to PostgreSQL shared memory, fast access to database.

Now anybody can using pgpool, pgbouncer, light httpd,  simple fast CGI script without problems.



If background worker is necessary, I am ready to realize it and it will be interesting to me.
But whether it will be more necessary for postgresql, than the free-standing application?


2015-03-23 19:24 GMT+03:00 Pavel Stehule <pavel.stehule@gmail.com>:
Hi

2015-03-22 23:28 GMT+01:00 Вадим Горбачев <bmsdave@gmail.com>:
Hi Team.

I would like to solve a problem of "Allow access to the database via HTTP".

But before drawing up the demand in GSOC I wanted to consult here. Therefore I will be grateful to comments from attendees here!

1. I think, will better use access to DB through the stand-alone program which not necessarily has to be on the same server. At least because it will give certain freedom in cluster systems.

2. Whether it is obligatory to use a programming language C for this purpose? After all as the stand-alone program ( frontend ) it has to be not necessarily written in the same programming language as the server ( backend ). I would prefer to use the python language for writing as I consider that this language is more clear to system administrators + to bring much more simply editings in a code.

What is a benefit of this implementation for Postgres community?

Proposed implementation is few lines in Python - and it is not big benefit for us. More, similar project exists.

It can be interesting as well integrated project to Postgres - implemented in C as background worker (if it possible)

Regards

Pavel
 

3. What you will advise what to pass a selection stage in GSOC 2015 from postgresql?)

PS: my English is poor. I ask you to forgive me for it.

Best Regards,
Vadim Gorbachov





Re: proposal GSoC 2015 task: Allow access to the database via HTTP

From
Вадим Горбачев
Date:
I came across correspondences:

as I understand, in this https://github.com/dobesv/restgres/project the idea of bgworker'a which listens to the specified port is already realized and processes http-inquiries = (

why then this task still is in the TODO sheet?

Re: proposal GSoC 2015 task: Allow access to the database via HTTP

From
Bruce Momjian
Date:
On Tue, Mar 24, 2015 at 11:19:08PM +0300, Вадим Горбачев wrote:
> I came across correspondences:
> http://www.postgresql.org/message-id/
> CAFjNrYu+Z1KfKt1..44K4pG69ou7fuHOw@mail.gmail.com
> 
> http://www .posatgresql.org/message-id/
> 9A28C8860F777E439AA12E8AEA7694F8FB8EAD@BPXM15GP.gisp.nec.co.jp
> as I understand, in this https://github.com/dobesv/restgres/project the idea of
> bgworker'a which listens to the specified port is already realized and
> processes http-inquiries = (
> 
> why then this task still is in the TODO sheet?

OK, removed from TODO.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



Re: proposal GSoC 2015 task: Allow access to the database via HTTP

From
Pavel Stehule
Date:


2015-03-24 21:19 GMT+01:00 Вадим Горбачев <bmsdave@gmail.com>:
I came across correspondences:

as I understand, in this https://github.com/dobesv/restgres/project the idea of bgworker'a which listens to the specified port is already realized and processes http-inquiries = (

why then this task still is in the TODO sheet?

because it is not in upstream yet ?

Pavel