Because sessions are extremely security sensitive (think 'SET ROLE', 'SET SESSION AUTHORIZATION') it's important that it not be possible to hijack them. A way to remain as stateless as possible where possible is desirable, but there'll also have to be a way to link requests to a particular backend's state. RESTful APIs tend to be largely stateless, but this isn't practical when working with PostgreSQL. The user session has state, including a possibly open transaction, a bunch of session specific GUCs, any open cursor(s), zero or more prepared statements, etc. PostgreSQL's FE/BE protocol uses long-lived TCP/IP connections with the strong concept of a user session. The POST HTTP verb should be used for all RPC-like operations. However this isn't always suitable for example, running a query is clearly an RPC operation and those endpoints are marked as such (as opposed to being considered a resource of some sort). The API is mainly following RESTful principles and many database objects are modeled as resources with their own URL. 4 How to represent and communicate sub-resources.This page is an early draft proposal of an extension to PostgreSQL allowing clients to access the database using HTTP instead of PostgreSQL's proprietary protocol (FEBE). Getting rid of that requirement would be nice (though won't solve the security challenges of directly exposing your database, of course).Ī HTTP REST API can make it very easy to traverse the database, making it discoverable and easily explored. Currently if you want to write, say, an Android app that talks to PostgreSQL you need to do it via a web API midlayer you host somewhere. HTTP+REST is much easier to use from mobile apps. Particularly so when combined with PostgreSQL's new built-in JSON types, which could be returned in a JSON format result unescaped as a directly nested child object. It'd also be attractive to the NoSQL crowd, who often want *simple* access. Such as curl, web browsers, new programming languages, etc. The benefit of an HTTP API would be easier access via tools that don't support the PostgreSQL protocol,

Pgadmin 4 no schema has been selected