What is the PostgreSQL Playground?
The Postgres Playground is an online PostgreSQL database that runs directly in your browser. It’s a simple, no-setup solution for testing SQL queries and learning PostgreSQL.
How long does data persist in the PostgreSQL Playground?
Data in the Postgres Playground is temporary. It is stored only in your browser’s memory and will disappear when you close or refresh the browser. It is not saved to disk or stored in browser local storage.
Is my data and code secure when using the PostgreSQL Playground?
Yes, your data and SQL code remain secure. All operations are executed locally in your browser, and we do not store your queries or data on any external servers.
Videos
Factsheet
30 years ago (1996-07-08)
30 years ago (1996-07-08)
Hi, I'm looking for some web hosting that would let me use PostgreSQL with a free plan on it. I'd like to experiment with triggers and listen/notifications, too.
I know there are some that offer this service, like AWS, but unlike it I would need that if my traffic/usage goes above the free plan the services just interrupts and let me choose if I wish to upgrade or not rather than directly billing me. Bonus points if it's easy to scale and not too expensive just in case my today's hobby becomes a production app some day.
If there's such a thing, please let me know. Appreciated!
From Postgres documentation - Client authentication is controlled by a configuration file, which traditionally is named pg_hba.conf and is stored in the database cluster's data directory. (HBA stands for host-based authentication.) Each record specifies a connection type, a client IP address range (if relevant for the connection type), a database name, a user name, and the authentication method to be used for connections matching these parameters.
So it is absolutely required to set up your pg_hba.conf for it to allow access to other computers. You will also need to setup router and firewall settings for allowing incoming connections to port 5432.
Here is what you need to do
on postgres.conf change listen_address to:
listen_addresses = '*'
and on pg_hba add this to the end of the file
host all all 0.0.0.0/0 md5
And also make sure the port is forwarded to the machine running Postgres from your router