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.
In our example, we use the SSH access and consider the following information:
We will use the default SSH users and databases, i.e. the ones created when the accounts are opened (e.g.
foo for 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:
- local: determines encoding,
- extensions: you can install PostgreSQL extensions with just a click (
PostGIS, etc.). If you need an extension that is not listed, you can contact support.
Several options :
use the following command :
$ xzcat $HOME/admin/backup/[date]/postgresql/[database].sql.xz | psql -h postgresql-[account].alwaysdata.net -U [user] -W -d [database]
get the tarbal and use the client of your choice.
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.