Shared Hosting for Everyone, imagined by developers, for developers.Discovering the Public Cloud
|Port||5432 (PostgreSQL port by default)|
The connection data depends on the relevant account. You can find the precise values in the administration interface section under Databases > PostgreSQL.
A pgBouncer is running on port
5433. It is possible to use it instead of PostgreSQL directly.
In our example, we use the SSH access and consider the following information:
foofor the foo account).
foo@ssh:~$ psql -h postgresql-foo.alwaysdata.net -U foo -W -d foo_base
When you create your PostgreSQL databases and users, you define the desired permissions, then our performs the following operations:
If you change your user’s permissions via a third party application, any validation via the administration interface (or via the API) will reset the permissions in line with the directives above.
On creating a database, you have the following options:
PostGIS, etc.). If you need an extension that is not listed, you can contact support.
Several options :
use our backup recovery feature,
use the following command :
$ zstdcat $HOME/admin/backup/[date]/postgresql/[database].sql.zst | psql -h postgresql-[account].alwaysdata.net -U [user] -W -d [database]
get the tarbal and use the client of your choice.
The maximum number of simultaneous connections per user is 50. On request, it is possible to change this for Private Cloud.
It is possible to see the names of all of the databases and users on the PostgreSQL servers. This is a limitation on PostgreSQL usage in a shared environment. Databases contents are NOT reachable.
Untrusted PostgreSQL languages, which executes arbitrary code with administrator privileges (running PostgreSQL), cannot be used on our servers.